CVE-2024-30384
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 Check for Unusual or Exceptional Conditions vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS on EX4300 Series allows a locally authenticated attacker with low privileges to cause a Denial-of-Service (Dos). If a specific CLI command is issued, a PFE crash will occur. This will cause traffic forwarding to be interrupted until the system self-recovers. This issue affects Junos OS: All versions before 20.4R3-S10, 21.2 versions before 21.2R3-S7, 21.4 versions before 21.4R3-S6.
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 locally authenticated low-privilege attacker can trigger a Packet Forwarding Engine (PFE) crash on Juniper EX4300 switches by issuing a specific CLI command, causing denial of service. The vulnerability stems from an improper check for unusual or exceptional conditions in the PFE.
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< 20.4= 20.4= 21.2= 21.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 Junos OS versionRun 'show version' command in CLI or check /var/etc/host VERSION fileAffected if Version is < 20.4, = 20.4, = 21.2, or = 21.4
-
Confirm EX4300 hardware modelRun 'show chassis hardware' or check 'show version' output for model informationAffected if Device model is EX4300 switch and version matches vulnerable ranges from step 1
-
Check for recent PFE crashesReview system logs using 'show log messages' and filter for PFE-related entries, or run 'show pfe statistics error'Affected if PFE crash events occurred and device is on a vulnerable version
Device is affected if it is an EX4300 switch running Junos OS versions 20.4, 21.2, 21.4, or any version below 20.4, and an attacker with low-privilege CLI access can trigger the vulnerability.
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 · scoped20.4
Upgrade Junos OS to fixed versions (20.4R3-S10, 21.2R3-S7, or 21.4R3-S6). Restrict CLI access to trusted low-privilege users and monitor for the specific trigger command.
20.4R3-S10, 21.2R3-S7, or 21.4R3-S6 (depending on which release branch you are on)
- 1. Identify the current Junos OS version on the EX4300 device using: show version
- 2. Based on current version, plan upgrade to the appropriate fixed release: 20.4R3-S10 or later, 21.2R3-S7 or later, or 21.4R3-S6 or later
- 3. Review Juniper release notes for the target version for any special upgrade instructions
- 4. Download the appropriate Junos OS upgrade package from Juniper Networks support portal
- 5. Upload the upgrade package to the device using: file copy or USB
- 6. Initiate the upgrade using: request system software add <package> reboot
- 7. After reboot, verify the new version using: show version and confirm the PFE is operational
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-30384 — 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-30384 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