Junos OS Evolved: Allocation of Resources Without Limits or Throttling
CVE-2024-47502 is a high-severity allocation of resources without limits or throttling vulnerability in Junos OS Evolved from Juniper Networks, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 21.4R3-S9-EVO, 22.2R3-S4-EVO, 22.4R3-S3-EVO as the first without the flaw, so updating Junos OS Evolved to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.64% chance of exploitation within 30 days, higher than 51% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Junos OS Evolved to 21.4R3-S9-EVO or 22.2R3-S4-EVO or 22.4R3-S3-EVO or 23.2R2-S1-EVO, whichever matches your release line, or a later version.
- Update junos_evolved to 21.4r3-s9-evo or 22.2r3-s4-evo or 22.4r3-s3-evo or 23.2r2-s1-evo, whichever matches your release line, or a later version.
- Read the advisory on supportportal.juniper.net for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Juniper Networks | Junos OS Evolved | before 21.4R3-S9-EVO; 22.2 up to, but not including, 22.2R3-S4-EVO; 22.4 up to, but not including, 22.4R3-S3-EVO; 23.2 up to, but not including, 23.2R2-S1-EVO; 23.4 up to, but not including, 23.4R2-EVO | 21.4R3-S9-EVO, 22.2R3-S4-EVO, 22.4R3-S3-EVO, 23.2R2-S1-EVO, 23.4R2-EVO |
| Juniper Networks | junos_evolved | before 21.4r3-s9-evo; 22.2 up to, but not including, 22.2r3-s4-evo; 22.4 up to, but not including, 22.4r3-s3-evo; 23.2 up to, but not including, 23.2r2-s1-evo; 23.4 up to, but not including, 23.4r2-evo | 21.4r3-s9-evo, 22.2r3-s4-evo, 22.4r3-s3-evo, 23.2r2-s1-evo, 23.4r2-evo |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by CNA (juniper.net).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 8.7 | High | CNA (juniper.net) |
| CVSS 3.1 | 7.5 | High | CNA (juniper.net) |
Official description
An Allocation of Resources Without Limits or Throttling vulnerability in the kernel of Juniper Networks Junos OS Evolved allows an unauthenticated, network based attacker to cause a Denial of Service (DoS). In specific cases the state of TCP sessions that are terminated is not cleared, which over time leads to an exhaustion of resources, preventing new connections to the control plane from being established. A continuously increasing number of connections shown by: user@host > show system connections is indicative of the problem. To recover the respective RE needs to be restarted manually. This issue only affects IPv4 but does not affect IPv6. This issue only affects TCP sessions established in-band (over an interface on an FPC) but not out-of-band (over the management ethernet port on the routing-engine). This issue affects Junos OS Evolved: * All versions before 21.4R3-S9-EVO, * 22.2 versions before 22.2R3-S4-EVO, * 22.4 version before 22.4R3-S3-EVO, * 23.2 versions before 23.2R2-S1-EVO, * 23.4 versions before 23.4R2-EVO.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Allocation of Resources Without Limits or Throttling
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
How developers prevent this class of flaw
- Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
- Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
More Allocation of Resources Without Limits or Throttling vulnerabilities (CWE-770)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other vulnerabilities in Junos OS Evolved
- 9.8 Critical severity
- 9.8 Critical severity
- 8.8 High severity
- 8.8 High severity
- 7.5 High severity
- 7.5 High severity
Recent Allocation of Resources Without Limits or Throttling vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.