{"schema_version":"2","view":"grouped","data":[{"id":67400,"cve_ids":["CVE-2016-0702","CVE-2016-0705","CVE-2016-0797"],"payload":{"kind":"patch","title":"Node.js 4.3.2 (LTS)","summary":"Node.js 4.3.2 upgrades OpenSSL to 1.0.2g, fixing defects associated with denial of service or memory corruption, and the CacheBleed side-channel attack.","evidence":"openssl: Upgrade from 1.0.2f to 1.0.2g","products":[{"name":{"value":"Node.js","evidence":"Node.js 4.3.2 (LTS)"},"prerequisites":[],"fixed_versions":[{"value":"4.3.2","evidence":"Node.js 4.3.2 (LTS)"}],"affected_versions":[]}],"severity":"low","fixed_cves":[],"related_cves":[{"value":"CVE-2016-0705","evidence":"More info is available at CVE-2016-0705."},{"value":"CVE-2016-0797","evidence":"More info is available at CVE-2016-0797."},{"value":"CVE-2016-0702","evidence":"More info is available at CVE-2016-0702."}],"security_relevant":true,"severity_evidence":"It is likely to be very difficult to use this defect for a practical attack and is therefore considered low severity for Node.js users."},"group_id":"advisory:3dc60eb9-33f3-4df3-807d-a23ecce17562","priority":{"reasons":[],"severity":"low","linked_cves":[],"fix_available":true,"known_exploited":false,"publisher_severity":"low"},"revision":1,"source_id":"nodejs","source_url":"https://nodejs.org/en/blog/release/v4.3.2","advisory_id":"3dc60eb9-33f3-4df3-807d-a23ecce17562","event_types":["patch"],"published_at":"2026-10-25T21:15:22.450979+00:00","technologies":["node-js","nodejs"],"context_update":false,"extraction_method":"llm","source_published_at":"2016-03-02T21:53:44+00:00","detail_url":"/advisories/advisory%3A3dc60eb9-33f3-4df3-807d-a23ecce17562","group":{"id":"advisory:3dc60eb9-33f3-4df3-807d-a23ecce17562","revision":1,"primary_event_id":67770,"change":"published","superseded_by":[],"changed":{"id":67770,"cve_ids":["CVE-2016-0702","CVE-2016-0705","CVE-2016-0797"],"payload":{"kind":"patch","title":"Node.js 4.3.2 (LTS)","summary":"Node.js 4.3.2 upgrades OpenSSL to 1.0.2g, fixing defects associated with denial of service or memory corruption, and the CacheBleed side-channel attack.","evidence":"openssl: Upgrade from 1.0.2f to 1.0.2g","products":[{"name":{"value":"Node.js","evidence":"Node.js 4.3.2 (LTS)"},"prerequisites":[],"fixed_versions":[{"value":"4.3.2","evidence":"Node.js 4.3.2 (LTS)"}],"affected_versions":[]}],"severity":"low","fixed_cves":[],"related_cves":[{"value":"CVE-2016-0705","evidence":"More info is available at CVE-2016-0705."},{"value":"CVE-2016-0797","evidence":"More info is available at CVE-2016-0797."},{"value":"CVE-2016-0702","evidence":"More info is available at CVE-2016-0702."}],"security_relevant":true,"severity_evidence":"It is likely to be very difficult to use this defect for a practical attack and is therefore considered low severity for Node.js users."},"group_id":"advisory:3dc60eb9-33f3-4df3-807d-a23ecce17562","priority":{"reasons":[],"severity":"low","linked_cves":[],"fix_available":true,"known_exploited":false,"publisher_severity":"low"},"revision":1,"source_id":"nodejs","source_url":"https://nodejs.org/en/blog/release/v4.3.2","advisory_id":"3dc60eb9-33f3-4df3-807d-a23ecce17562","event_types":["patch"],"published_at":"2026-10-25T21:15:22.450979+00:00","technologies":["node-js","nodejs"],"context_update":false,"extraction_method":"llm","source_published_at":"2016-03-02T21:53:44+00:00","detail_url":"/events/67770"},"members":[{"id":67770,"cve_ids":["CVE-2016-0702","CVE-2016-0705","CVE-2016-0797"],"payload":{"kind":"patch","title":"Node.js 4.3.2 (LTS)","summary":"Node.js 4.3.2 upgrades OpenSSL to 1.0.2g, fixing defects associated with denial of service or memory corruption, and the CacheBleed side-channel attack.","evidence":"openssl: Upgrade from 1.0.2f to 1.0.2g","products":[{"name":{"value":"Node.js","evidence":"Node.js 4.3.2 (LTS)"},"prerequisites":[],"fixed_versions":[{"value":"4.3.2","evidence":"Node.js 4.3.2 (LTS)"}],"affected_versions":[]}],"severity":"low","fixed_cves":[],"related_cves":[{"value":"CVE-2016-0705","evidence":"More info is available at CVE-2016-0705."},{"value":"CVE-2016-0797","evidence":"More info is available at CVE-2016-0797."},{"value":"CVE-2016-0702","evidence":"More info is available at CVE-2016-0702."}],"security_relevant":true,"severity_evidence":"It is likely to be very difficult to use this defect for a practical attack and is therefore considered low severity for Node.js users."},"group_id":"advisory:3dc60eb9-33f3-4df3-807d-a23ecce17562","priority":{"reasons":[],"severity":"low","linked_cves":[],"fix_available":true,"known_exploited":false,"publisher_severity":"low"},"revision":1,"source_id":"nodejs","source_url":"https://nodejs.org/en/blog/release/v4.3.2","advisory_id":"3dc60eb9-33f3-4df3-807d-a23ecce17562","event_types":["patch"],"published_at":"2026-10-25T21:15:22.450979+00:00","technologies":["node-js","nodejs"],"context_update":false,"extraction_method":"llm","source_published_at":"2016-03-02T21:53:44+00:00","detail_url":"/events/67770"}]}},{"id":67286,"cve_ids":["CVE-2016-0702","CVE-2016-0705","CVE-2016-0797"],"payload":{"kind":"patch","title":"Node.js 5.7.1 security fixes","summary":"Node.js 5.7.1 upgrades OpenSSL to 1.0.2g and includes fixes for defects associated with three CVEs. The announcement describes the issues as low severity for Node.js users or unlikely to enable practical attacks in Node.js.","evidence":"Node.js 5.7.1 (Current)","products":[{"name":{"value":"Node.js","evidence":"Node.js 5.7.1 (Current)"},"prerequisites":[],"fixed_versions":[{"value":"5.7.1","evidence":"Node.js 5.7.1 (Current)"}],"affected_versions":[]}],"severity":"low","fixed_cves":[],"related_cves":[{"value":"CVE-2016-0705","evidence":"More info is available at CVE-2016-0705."},{"value":"CVE-2016-0797","evidence":"More info is available at CVE-2016-0797."},{"value":"CVE-2016-0702","evidence":"More info is available at CVE-2016-0702."}],"security_relevant":true,"severity_evidence":"It is likely to be very difficult to use this defect for a practical attack and is therefore considered low severity for Node.js users."},"group_id":"advisory:db8f65bd-8b7e-497e-ba3f-aa924c01d2a8","priority":{"reasons":[],"severity":"low","linked_cves":[],"fix_available":true,"known_exploited":false,"publisher_severity":"low"},"revision":1,"source_id":"nodejs","source_url":"https://nodejs.org/en/blog/release/v5.7.1","advisory_id":"db8f65bd-8b7e-497e-ba3f-aa924c01d2a8","event_types":["patch"],"published_at":"2026-10-25T21:13:25.580012+00:00","technologies":["node-js","nodejs"],"context_update":false,"extraction_method":"llm","source_published_at":"2016-03-02T23:23:06+00:00","detail_url":"/advisories/advisory%3Adb8f65bd-8b7e-497e-ba3f-aa924c01d2a8","group":{"id":"advisory:db8f65bd-8b7e-497e-ba3f-aa924c01d2a8","revision":1,"primary_event_id":67656,"change":"published","superseded_by":[],"changed":{"id":67656,"cve_ids":["CVE-2016-0702","CVE-2016-0705","CVE-2016-0797"],"payload":{"kind":"patch","title":"Node.js 5.7.1 security fixes","summary":"Node.js 5.7.1 upgrades OpenSSL to 1.0.2g and includes fixes for defects associated with three CVEs. The announcement describes the issues as low severity for Node.js users or unlikely to enable practical attacks in Node.js.","evidence":"Node.js 5.7.1 (Current)","products":[{"name":{"value":"Node.js","evidence":"Node.js 5.7.1 (Current)"},"prerequisites":[],"fixed_versions":[{"value":"5.7.1","evidence":"Node.js 5.7.1 (Current)"}],"affected_versions":[]}],"severity":"low","fixed_cves":[],"related_cves":[{"value":"CVE-2016-0705","evidence":"More info is available at CVE-2016-0705."},{"value":"CVE-2016-0797","evidence":"More info is available at CVE-2016-0797."},{"value":"CVE-2016-0702","evidence":"More info is available at CVE-2016-0702."}],"security_relevant":true,"severity_evidence":"It is likely to be very difficult to use this defect for a practical attack and is therefore considered low severity for Node.js users."},"group_id":"advisory:db8f65bd-8b7e-497e-ba3f-aa924c01d2a8","priority":{"reasons":[],"severity":"low","linked_cves":[],"fix_available":true,"known_exploited":false,"publisher_severity":"low"},"revision":1,"source_id":"nodejs","source_url":"https://nodejs.org/en/blog/release/v5.7.1","advisory_id":"db8f65bd-8b7e-497e-ba3f-aa924c01d2a8","event_types":["patch"],"published_at":"2026-10-25T21:13:25.580012+00:00","technologies":["node-js","nodejs"],"context_update":false,"extraction_method":"llm","source_published_at":"2016-03-02T23:23:06+00:00","detail_url":"/events/67656"},"members":[{"id":67656,"cve_ids":["CVE-2016-0702","CVE-2016-0705","CVE-2016-0797"],"payload":{"kind":"patch","title":"Node.js 5.7.1 security fixes","summary":"Node.js 5.7.1 upgrades OpenSSL to 1.0.2g and includes fixes for defects associated with three CVEs. The announcement describes the issues as low severity for Node.js users or unlikely to enable practical attacks in Node.js.","evidence":"Node.js 5.7.1 (Current)","products":[{"name":{"value":"Node.js","evidence":"Node.js 5.7.1 (Current)"},"prerequisites":[],"fixed_versions":[{"value":"5.7.1","evidence":"Node.js 5.7.1 (Current)"}],"affected_versions":[]}],"severity":"low","fixed_cves":[],"related_cves":[{"value":"CVE-2016-0705","evidence":"More info is available at CVE-2016-0705."},{"value":"CVE-2016-0797","evidence":"More info is available at CVE-2016-0797."},{"value":"CVE-2016-0702","evidence":"More info is available at CVE-2016-0702."}],"security_relevant":true,"severity_evidence":"It is likely to be very difficult to use this defect for a practical attack and is therefore considered low severity for Node.js users."},"group_id":"advisory:db8f65bd-8b7e-497e-ba3f-aa924c01d2a8","priority":{"reasons":[],"severity":"low","linked_cves":[],"fix_available":true,"known_exploited":false,"publisher_severity":"low"},"revision":1,"source_id":"nodejs","source_url":"https://nodejs.org/en/blog/release/v5.7.1","advisory_id":"db8f65bd-8b7e-497e-ba3f-aa924c01d2a8","event_types":["patch"],"published_at":"2026-10-25T21:13:25.580012+00:00","technologies":["node-js","nodejs"],"context_update":false,"extraction_method":"llm","source_published_at":"2016-03-02T23:23:06+00:00","detail_url":"/events/67656"}]}}],"next_after":67400,"next_before":67286}