Junos OS: SRX Series: Insufficient certificate verification for device to SD cloud communication
Noroxi assessment
Priority: Monitor (action score 33/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Juniper Networks Junos OS 22.4R3-S9, 23.2R2-S6, 23.4R2-S7.
Low priority for now. Upgrade to Juniper Networks Junos OS 22.4R3-S9, 23.2R2-S6, 23.4R2-S7 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Apr 9, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- CWE-296
Report tools
Action score
33
Monitor
Low priority for now.
- CVSS
- 33 / 40 · 8.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · juniper
- 6.5
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| juniper | junos | cpe:2.3:o:juniper:junos |
| juniper | srx1500 | cpe:2.3:h:juniper:srx1500 |
| juniper | srx1600 | cpe:2.3:h:juniper:srx1600 |
| juniper | srx2300 | cpe:2.3:h:juniper:srx2300 |
| juniper | srx300 | cpe:2.3:h:juniper:srx300 |
| juniper | srx320 | cpe:2.3:h:juniper:srx320 |
| juniper | srx340 | cpe:2.3:h:juniper:srx340 |
| juniper | srx345 | cpe:2.3:h:juniper:srx345 |
| juniper | srx380 | cpe:2.3:h:juniper:srx380 |
| juniper | srx4100 | cpe:2.3:h:juniper:srx4100 |
| juniper | srx4120 | cpe:2.3:h:juniper:srx4120 |
| juniper | srx4200 | cpe:2.3:h:juniper:srx4200 |
and 6 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- juniper junosbefore 22.4
- juniper junos22.4
- juniper junos23.2
- juniper junos23.4
- juniper junos24.2
- juniper junos24.4
- juniper junos25.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (juniper). Independent of NVD's CPE analysis and usually ahead of it.
Juniper Networks Junos OS
- before 22.4R3-S9affected · semver
- 23.2 and later · before 23.2R2-S6affected · semver
- 23.4 and later · before 23.4R2-S7affected · semver
- 24.2 and later · before 24.2R2-S3affected · semver
- 24.4 and later · before 24.4R2-S2affected · semver
- 25.2 and later · before 25.2R1-S2, 25.2R2affected · semver
Same product
juniper: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-36845Junos OS: EX and SRX Series: A PHP vulnerability in J-Web allows an unauthenticated to control an important environment variableKEV98Now
- CVE-2023-36846Junos OS: SRX Series: A vulnerability in J-Web allows an unauthenticated attacker to upload arbitrary filesKEV79This week
- CVE-2023-36844Junos OS: EX Series: A PHP vulnerability in J-Web allows an unauthenticated attacker to control important environment variablesKEV78This week
Published before and after this one in the same product
- ← EarlierCVE-2026-33776Apr 9, 2026 · Junos OS and Junos OS Evolved: Specific low privileged CLI command exposes sensitive information27Monitor
- ← EarlierCVE-2026-33778Apr 9, 2026 · Junos OS: SRX Series, MX Series: When a specifically malformed first ISAKMP packet is received kmd/iked crashes34Monitor
- Later →CVE-2026-33780Apr 9, 2026 · Junos OS and Junos OS Evolved: In an EVPN-MPLS scenario churn of ESI routes causes a memory leak in l2ald28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Juniper Networks Junos OS | 22.4R3-S9 | Vendor (CNA) |
| Juniper Networks Junos OS | 23.2R2-S6 | Vendor (CNA) |
| Juniper Networks Junos OS | 23.4R2-S7 | Vendor (CNA) |
| Juniper Networks Junos OS | 24.2R2-S3 | Vendor (CNA) |
| Juniper Networks Junos OS | 24.4R2-S2 | Vendor (CNA) |
| Juniper Networks Junos OS | 25.2R1-S2, 25.2R2 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Konrad Porzezynskifinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-296 · Improper Following of a Certificate's Chain of TrustCVSS vector
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:M/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.