CVE-2024-30390
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 Improper Restriction of Excessive Authentication Attempts vulnerability in Juniper Networks Junos OS Evolved allows an unauthenticated, network-based attacker to cause a limited Denial of Service (DoS) to the management plane. When an incoming connection was blocked because it exceeded the connections-per-second rate-limit, the system doesn't consider existing connections anymore for subsequent connection attempts so that the connection limit can be exceeded. This issue affects Junos OS Evolved: * All versions before 21.4R3-S4-EVO, * 22.1-EVO versions before 22.1R3-S3-EVO, * 22.2-EVO versions before 22.2R3-S2-EVO, * 22.3-EVO versions before 22.3R2-S1-EVO, 22.3R3-EVO.
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 confidenceA vulnerability in Juniper Junos OS Evolved causes the system to ignore existing connections when rate-limiting blocks incoming connections due to exceeding the connections-per-second limit. This allows an unauthenticated attacker to cause a DoS by exceeding the connection limit through repeated connection attempts that should have been rate-limited.
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.1= 22.2= 22.3CVSS 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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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 Junos OS Evolved versionRun 'show version' or 'show version detail' to obtain the installed Junos OS Evolved versionAffected if The installed version is < 21.4, = 21.4, = 22.1, = 22.2, or = 22.3
-
Verify if rate-limiting is configuredCheck configuration for rate-limiting or connection limits using 'show configuration | match rate-limit' or 'show configuration | match connections-per-second'Affected if Rate-limiting with connections-per-second limits is configured and active on the system
-
Check for SYN flood or connection protection servicesRun 'show services' or review firewall filter configurations that include SYN flood protection, connection limits, or rate-limiting policiesAffected if SYN flood protection or connection-rate limiting services are enabled
-
Review connection table for anomaliesRun 'show system connections' or 'show security flow session' to inspect active connections and look for patterns of excessive half-open connectionsAffected if There is a high volume of connection attempts or sessions that bypass existing rate limits
-
Confirm the system is exposed to unauthenticated network connectionsReview interface configurations and security policies using 'show configuration interfaces' and 'show configuration security' to determine if services accepting external connections are exposedAffected if The system accepts unauthenticated connections from untrusted networks on services subject to rate-limiting
A system is affected if it runs Junos OS Evolved version 21.4, 22.1, 22.2, or 22.3 (or any version below 21.4) with rate-limiting configured for connections-per-second on exposed network services.
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
Upgrade Junos OS Evolved to a patched version as specified in the vendor advisory (21.4R3-S4-EVO, 22.1R3-S3-EVO, 22.2R3-S2-EVO, 22.3R2-S1-EVO, or 22.3R3-EVO).
Upgrade to 21.4R3-S4-EVO or later for 21.4.x; 22.1R3-S3-EVO or later for 22.1.x; 22.2R3-S2-EVO or later for 22.2.x; 22.3R2-S1-EVO or 22.3R3-EVO for 22.3.x
- 1. Identify the current Junos OS Evolved version running on the device using 'show version' command
- 2. Determine which upgrade path applies based on current version (21.4.x, 22.1.x, 22.2.x, or 22.3.x)
- 3. Download the appropriate fixed EVO image from Juniper Networks support portal
- 4. Upload the software package to the device using 'file copy' or USB transfer
- 5. Install the software using 'request system software add <package> reboot' command
- 6. Verify the upgrade completed successfully with 'show version' and confirm the new version includes the fix
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-30390 — 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-30390 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