Junos OS: SRX Series: Insufficient certificate verification for device to SD cloud communication
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 22.4R3-S9, 23.2R2-S6, 23.4R2-S7, 24.2R2-S3, 24.4R2-S2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
An Improper Following of a Certificate's Chain of Trust vulnerability in J-Web of Juniper Networks Junos OS on SRX Series allows a PITM to intercept the communication of the device and get access to confidential information and potentially modify it. When an SRX device is provisioned to connect to Security Director (SD) cloud, it doesn't perform sufficient verification of the received server certificate. This allows a PITM to intercept the communication between the SRX and SD cloud and access credentials and other sensitive information. This issue affects Junos OS: • all versions before 22.4R3-S9, • 23.2 versions before 23.2R2-S6, • 23.4 versions before 23.4R2-S7, • 24.2 versions before 24.2R2-S3, • 24.4 versions before 24.4R2-S2, • 25.2 versions before 25.2R1-S2, 25.2R2.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Juniper Networks Junos OS
fixed in 22.4R3-S9; From 23.2 · fixed in 23.2R2-S6; From 23.4 · fixed in 23.4R2-S7; From 24.2 · fixed in 24.2R2-S3; From 24.4 · fixed in 24.4R2-S2