CVE-2024-21610: Junos OS: If in a scaled CoS scenario information on CoS state is gathered mgd processes get stuck
Noroxi assessment
Priority: Monitor (action score 21/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.47% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Juniper Networks Junos OS 20.4R3-S9, 21.2R3-S7, 21.3R3-S5.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Juniper Networks Junos OS 20.4R3-S9, 21.2R3-S7, 21.3R3-S5 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 Handling of Exceptional Conditions vulnerability in the Class of Service daemon (cosd) of Juniper Networks Junos OS allows an authenticated, network-based attacker with low privileges to cause a limited Denial of Service (DoS). In a scaled CoS scenario with 1000s of interfaces, when specific low privileged commands, received over NETCONF, SSH or telnet, are handled by cosd on behalf of mgd, the respective child management daemon (mgd) processes will get stuck. In case of (Netconf over) SSH this leads to stuck SSH sessions, so that when the connection-limit for SSH is reached, new sessions can't be established anymore. A similar behavior will be seen for telnet etc. Stuck mgd processes can be monitored by executing the following command: user@host> show system processes extensive | match mgd | match sbwait This issue affects Juniper Networks Junos OS: * All versions earlier than 20.4R3-S9; * 21.2 versions earlier than 21.2R3-S7; * 21.3 versions earlier than 21.3R3-S5; * 21.4 versions earlier than 21.4R3-S5; * 22.1 versions earlier than 22.1R3-S4; * 22.2 versions earlier than 22.2R3-S3; * 22.3 versions earlier than 22.3R3-S2; * 22.4 versions earlier than 22.4R3; * 23.2 versions earlier than 23.2R1-S2, 23.2R2.
- Published
- Apr 12, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 41th percentile
- CWE
- CWE-755
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · juniper
- 4.3
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
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 | mx | cpe:2.3:h:juniper:mx |
| juniper | mx10 | cpe:2.3:h:juniper:mx10 |
| juniper | mx10000 | cpe:2.3:h:juniper:mx10000 |
| juniper | mx10003 | cpe:2.3:h:juniper:mx10003 |
| juniper | mx10004 | cpe:2.3:h:juniper:mx10004 |
| juniper | mx10008 | cpe:2.3:h:juniper:mx10008 |
| juniper | mx10016 | cpe:2.3:h:juniper:mx10016 |
| juniper | mx104 | cpe:2.3:h:juniper:mx104 |
| juniper | mx150 | cpe:2.3:h:juniper:mx150 |
| juniper | mx2008 | cpe:2.3:h:juniper:mx2008 |
| juniper | mx2010 | cpe:2.3:h:juniper:mx2010 |
and 9 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- juniper junosbefore 20.4
- juniper junos20.4
- juniper junos21.2
- juniper junos21.3
- juniper junos21.4
- juniper junos22.1
- juniper junos22.2
- juniper junos22.3
- juniper junos22.4
- juniper junos23.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 20.4R3-S9affected · semver
- 21.2 and later · before 21.2R3-S7affected · semver
- 21.3 and later · before 21.3R3-S5affected · semver
- 21.4 and later · before 21.4R3-S5affected · semver
- 22.1 and later · before 22.1R3-S4affected · semver
- 22.2 and later · before 22.2R3-S3affected · semver
- 22.3 and later · before 22.3R3-S2affected · semver
- 22.4 and later · before 22.4R3affected · semver
- 23.2 and later · before 23.2R1-S2, 23.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-2024-21605Apr 12, 2024 · Junos OS: SRX 300 Series: Specific link local traffic causes a control plane overload28Monitor
- ← EarlierCVE-2024-21609Apr 12, 2024 · Junos OS: MX Series with SPC3, and SRX Series: If specific IPsec parameters are negotiated iked will crash due to a memory leak28Monitor
- Later →CVE-2024-21615Apr 12, 2024 · Junos OS and Junos OS Evolved: A low-privileged user can access confidential information20Monitor
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 | 20.4R3-S9 | Vendor (CNA) |
| Juniper Networks Junos OS | 21.2R3-S7 | Vendor (CNA) |
| Juniper Networks Junos OS | 21.3R3-S5 | Vendor (CNA) |
| Juniper Networks Junos OS | 21.4R3-S5 | Vendor (CNA) |
| Juniper Networks Junos OS | 22.1R3-S4 | Vendor (CNA) |
| Juniper Networks Junos OS | 22.2R3-S3 | Vendor (CNA) |
| Juniper Networks Junos OS | 22.3R3-S2 | Vendor (CNA) |
| Juniper Networks Junos OS | 22.4R3 | Vendor (CNA) |
| Juniper Networks Junos OS | 23.2R1-S2, 23.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.
No history yet (it accumulates with the daily EPSS job).
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.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-303820 days apartJunos OS and Junos OS Evolved: RPD crash when CoS-based forwarding (CBF) policy is configured34Monitor
- CVE-2024-3955589 days apartJunos OS and Junos OS Evolved: Receipt of a specific malformed BGP update causes the session to reset34Monitor
- CVE-2024-3955290 days apartJunos OS and Junos OS Evolved: Malformed BGP UPDATE causes RPD crash34Monitor
- CVE-2024-39525180 days apartJunos OS and Junos OS Evolved: When BGP traceoptions is enabled, receipt of specially crafted BGP packet causes RPD crash34Monitor
- CVE-2024-47491182 days apartJunos OS and Junos OS Evolved: Receipt of a specific malformed BGP path attribute leads to an RPD crash32Monitor
- CVE-2025-52948455 days apartJunos OS: Specific unknown traffic pattern causes FPC and system to crash when packet capturing is enabled32Monitor
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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0279 · Apr 15, 2024(Juniper Güvenlik Bildirimi)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-755 · Improper Handling of Exceptional ConditionsCVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/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:X/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
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.