CVE-2020-1628
Junos OS: EX4300: Traffic from the network internal to the device (128.0.0.0) may be forwarded to egress interfaces
- Published
- Updated
- Reserved
- Assigned by
- juniper
Description
Juniper Networks Junos OS uses the 128.0.0.0/2 subnet for internal communications between the RE and PFEs. It was discovered that packets utilizing these IP addresses may egress an EX4300 switch, leaking configuration information such as heartbeats, kernel versions, etc. out to the Internet, leading to an information exposure vulnerability. This issue affects Juniper Networks Junos OS: 14.1X53 versions prior to 14.1X53-D53 on EX4300; 15.1 versions prior to 15.1R7-S6 on EX4300; 15.1X49 versions prior to 15.1X49-D200, 15.1X49-D210 on EX4300; 16.1 versions prior to 16.1R7-S7 on EX4300; 17.1 versions prior to 17.1R2-S11, 17.1R3-S2 on EX4300; 17.2 versions prior to 17.2R3-S3 on EX4300; 17.3 versions prior to 17.3R2-S5, 17.3R3-S7 on EX4300; 17.4 versions prior to 17.4R2-S9, 17.4R3 on EX4300; 18.1 versions prior to 18.1R3-S8 on EX4300; 18.2 versions prior to 18.2R3-S2 on EX4300; 18.3 versions prior to 18.3R2-S3, 18.3R3, 18.3R3-S1 on EX4300; 18.4 versions prior to 18.4R1-S5, 18.4R2-S3, 18.4R3 on EX4300; 19.1 versions prior to 19.1R1-S4, 19.1R2 on EX4300; 19.2 versions prior to 19.2R1-S4, 19.2R2 on EX4300; 19.3 versions prior to 19.3R1-S1, 19.3R2 on EX4300.
Timeline
ID reserved
By juniper
- 5 months later
· 5 months later
Published
- 4 years later
· 4 years later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| juniperCNA (assigner) | 3.1 | Medium5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVDNVD · Modified | 3.1 | Medium5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
- EPSS (exploitation in 30 days)
- 1.3% · top 29% of all CVEs (7 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.3.
Weakness
Affected products
- affected 14.1X53 – < 14.1X53-D53
- affected 15.1 – < 15.1R7-S6
- affected 15.1X49 – < 15.1X49-D200, 15.1X49-D210
- affected 16.1 – < 16.1R7-S7
- affected 17.1 – < 17.1R2-S11, 17.1R3-S2
- affected 17.2 – < 17.2R3-S3
- affected 17.3 – < 17.3R2-S5, 17.3R3-S7
- affected 17.4 – < 17.4R2-S9, 17.4R3
- affected 18.1 – < 18.1R3-S8
- affected 18.2 – < 18.2R3-S2
- affected 18.3 – < 18.3R2-S3, 18.3R3, 18.3R3-S1
- affected 18.4 – < 18.4R1-S5, 18.4R2-S3, 18.4R3
- affected 19.1 – < 19.1R1-S4, 19.1R2
- affected 19.2 – < 19.2R1-S4, 19.2R2
- affected 19.3 – < 19.3R1-S1, 19.3R2
What to do
Solution: The following software releases have been updated to resolve this specific issue: 14.1X53-D53, 15.1R7-S6, 15.1X49-D200, 15.1X49-D210, 16.1R7-S7, 17.1R2-S11, 17.1R3-S2, 17.2R3-S3, 17.3R2-S5, 17.3R3-S7, 17.4R2-S9, 17.4R3, 18.1R3-S8, 18.2R3-S2, 18.3R2-S3, 18.3R3, 18.3R3-S1, 18.4R1-S5, 18.4R2-S3, 18.4R3, 19.1R1-S4, 19.1R2, 19.2R1-S4, 19.2R2, 19.3R1-S1, 19.3R2, 19.4R1, and all subsequent releases.
Workaround: Configure a firewall filter to discard packets sourced from the internal network. Disabling the net.transit_re sysctl flag will also cause management traffic forwarded to the PFE ports to be dropped: % sysctl -w net.transit_re=0 Note that sysctl flags do not survive a reboot.
Exploitation: Juniper SIRT is not aware of any malicious exploitation of this vulnerability.
References (1)
- https://kb.juniper.net/JSA11008 (opens in a new tab)x_refsource_CONFIRMx_transferred
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2020-1628)Record last updated .