CVE-2024-47497
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn Uncontrolled Resource Consumption vulnerability in the http daemon (httpd) of Juniper Networks Junos OS on SRX Series, QFX Series, MX Series and EX Series allows an unauthenticated, network-based attacker to cause Denial-of-Service (DoS). An attacker can send specific HTTPS connection requests to the device, triggering the creation of processes that are not properly terminated. Over time, this leads to resource exhaustion, ultimately causing the device to crash and restart. The following command can be used to monitor the resource usage: user@host> show system processes extensive | match mgd | count This issue affects Junos OS on SRX Series and EX Series: All versions before 21.4R3-S7, from 22.2 before 22.2R3-S4, from 22.3 before 22.3R3-S3, from 22.4 before 22.4R3-S2, from 23.2 before 23.2R2-S1, from 23.4 before 23.4R1-S2, 23.4R2.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAn unauthenticated network attacker can send specific HTTPS requests to Junos OS httpd on SRX, QFX, MX, and EX Series devices, causing improperly terminated processes to accumulate. Over time, this resource exhaustion leads to device crash and restart (DoS).
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 21.4= 21.4= 22.2= 22.3= 22.4= 23.2= 23.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelRun 'show chassis hardware' or 'show version' to confirm the device is an SRX, QFX, MX, or EX Series deviceAffected if Device is not one of these series, then it is not affected by this CVE
-
Check the Junos OS versionRun 'show version' and compare the installed version against the affected ranges: < 21.4, 21.4, 22.2, 22.3, 22.4, 23.2, or 23.4Affected if The installed version matches any of the listed versions or is earlier than 21.4
-
Verify httpd service is enabledRun 'show system services' or check the httpd process status with 'show system processes' | grep httpd'Affected if httpd is enabled and listening on HTTPS ports; if disabled, the attack surface is reduced
-
Monitor for process accumulationRun 'show system processes extensive' repeatedly over time to observe if httpd child processes are improperly terminating and accumulatingAffected if Processes are accumulating without being cleaned up, indicating the vulnerability may be triggered
If the device is an SRX, QFX, MX, or EX Series running an affected Junos OS version (21.4, 22.2, 22.3, 22.4, 23.2, 23.4, or any version below 21.4) with httpd enabled and accessible over the network, the environment is vulnerable to CVE-2024-47497.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped21.4
Apply the appropriate Junos OS software patch per the version matrix (21.4R3-S7, 22.2R3-S4, 22.3R3-S3, 22.4R3-S2, 23.2R2-S1, 23.4R1-S2 or later). If immediate patching is not feasible, consider disabling httpd or implementing firewall filters to limit HTTPS exposure to untrusted networks.
Upgrade to 21.4R3-S7, 22.2R3-S4, 22.3R3-S3, 22.4R3-S2, 23.2R2-S1, or 23.4R1-S2/23.4R3 or later (22.4R3-S2 recommended for broadest coverage)
- 1. Identify the current Junos OS version on the device using 'show version'
- 2. Determine the appropriate upgrade path based on the device series (SRX, QFX, MX, EX)
- 3. Download the fixed Junos OS version from Juniper Networks support portal
- 4. Upload the Junos OS upgrade package to the device
- 5. Install the upgrade using 'request system software add <package>'
- 6. Reboot the device using 'request system reboot'
- 7. After reboot, verify the new version is installed with 'show version'
- 8. Monitor process resource usage using 'show system processes extensive | match mgd | count' to confirm the issue is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47497 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-47497 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data