{"id":"CVE-2018-0014","url":"https://www.cyber-defence.io/tools/cve/CVE-2018-0014","generatedAt":"2026-10-29T00:35:17.377Z","title":"Juniper Networks ScreenOS devices do not pad Ethernet packets with zeros, and thus some packets can contain fragments of system memory or data from previous packets.","description":"Juniper Networks ScreenOS devices do not pad Ethernet packets with zeros, and thus some packets can contain fragments of system memory or data from previous packets. This issue is often detected as CVE-2003-0001. The issue affects all versions of Juniper Networks ScreenOS prior to 6.3.0r25.","published":"2018-01-10T22:29:01.000Z","lastModified":"2026-06-17T01:29:23.000Z","status":"Modified","sourceIdentifier":"sirt@juniper.net","cvss":{"version":"3.0","score":6.5,"severity":"MEDIUM","vector":"CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"},"cwe":["CWE-200"],"affected":["juniper/screenos"],"epss":{"score":0.00603,"percentile":0.4866,"date":"2026-10-27","history":[]},"kev":{"listed":false},"exploits":{"count":0,"verified":false,"firstPublished":null,"source":"Exploit-DB (https://gitlab.com/exploit-database/exploitdb)","entries":[]},"verdict":{"level":"low","text":"Lower severity and a low EPSS score (0.60%). Track it; it rarely justifies an emergency change on its own."},"changes":[],"references":[{"url":"http://www.securitytracker.com/id/1040185","tags":["Third Party Advisory","VDB Entry"],"source":"sirt@juniper.net"},{"url":"https://kb.juniper.net/JSA10841","tags":["Vendor Advisory"],"source":"sirt@juniper.net"},{"url":"http://www.securitytracker.com/id/1040185","tags":["Third Party Advisory","VDB Entry"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://kb.juniper.net/JSA10841","tags":["Vendor Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"}],"sources":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2018-0014","epss":"https://www.first.org/epss/","kev":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","exploitdb":"https://www.exploit-db.com/"},"licence":"CC BY 4.0 — link back to the CVE Explorer if you publish the results; upstream data remains subject to its own terms."}