ScreenOS: Etherleak vulnerability found on ScreenOS device

published 2018-01-10 8y ago modified 2026-06-17 4mo ago also EUVD-2018-0839

cvss: 4.3; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.6%; EPSS 0.6% chance of exploitation in 30 days, percentile 49%
public exploits: 0; none known

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.

Patch / fix

fixed in 1

Juniper Networks ScreenOS 6.3.0r25

Is CVE-2018-0014 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.60% chance of exploitation in the next 30 days, higher than 49% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.0	4.3	CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD	3.0	6.5	CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD	2.0	3.3	AV:A/AC:L/Au:N/C:P/I:N/A:N

Affected products

Juniper Networks ScreenOS

Classification

Weakness

CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

kb.juniper.net /JSA10841
vendor-advisory
securitytracker.com /id/1040185
vdb-entry, third-party-advisory

Sources

CVE List CVE-2018-0014
NVD CVE-2018-0014

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.