dbcve.org
JunosOperating system · Juniper

CVE-2024-30401

MEDIUM · 5.9 CVSS v3.1 Published 2024-04-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
An Out-of-bounds Read vulnerability in the advanced forwarding management process aftman of Juniper Networks Junos OS on MX Series with MPC10E, MPC11, MX10K-LC9600 line cards, MX304, and EX9200-15C, may allow an attacker to exploit a stack-based buffer overflow, leading to a reboot of the FPC. Through code review, it was determined that the interface definition code for aftman could read beyond a buffer boundary, leading to a stack-based buffer overflow. This issue affects Junos OS on MX Series and EX9200-15C: * from 21.2 before 21.2R3-S1, * from 21.4 before 21.4R3, * from 22.1 before 22.1R2, * from 22.2 before 22.2R2;  This issue does not affect: * versions of Junos OS prior to 20.3R1; * any version of Junos OS 20.4.

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 confidence

An out-of-bounds read vulnerability exists in the advanced forwarding management process (aftman) of Juniper Networks Junos OS on MX Series with specific MPC line cards and EX9200-15C. The interface definition code reads beyond a buffer boundary, causing a stack-based buffer overflow that can trigger FPC reboots.

MitigationUpgrade Junos OS to version 21.2R3-S1, 21.4R3, 22.1R2, 22.2R2 or later to address the buffer overflow vulnerability in aftman.

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
JunosOperating system
Affected:= 21.2= 21.4= 22.1= 22.2

CVSS 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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Run 'show chassis hardware' or check the device model to confirm it is an MX Series router or EX9200-15C switch.
    Affected if Device is not an MX Series router or EX9200-15C switch.
  2. Check Junos OS version
    Run 'show version' and note the Junos OS version installed.
    Affected if Version matches 21.2, 21.4, 22.1, or 22.2 (exact versions listed in the affected range).
  3. Verify MPC line card presence
    Run 'show chassis fpc' or 'show chassis hardware' to list installed MPC line cards.
    Affected if The device has MPC line cards installed (the vulnerability affects MX Series with specific MPCs).
  4. Confirm aftman process availability
    Run 'ps aux | grep aftman' or check process status via 'show system processes' to verify the advanced forwarding management process is present.
    Affected if The aftman process is running on the device.

A user is affected if they run Junos OS versions 21.2, 21.4, 22.1, or 22.2 on an MX Series router or EX9200-15C with MPC line cards, where the aftman process is active.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Junos OS to version 21.2R3-S1, 21.4R3, 22.1R2, 22.2R2 or later to address the buffer overflow vulnerability in aftman.

Recommended fix High confidence

21.2R3-S1, 21.4R3, 22.1R2, or 22.2R2 (depending on current branch)

  1. 1. Identify the current Junos OS version running on the affected device using 'show version'
  2. 2. Determine which affected version branch is currently installed (21.2, 21.4, 22.1, or 22.2)
  3. 3. For devices on 21.2 branch: upgrade to 21.2R3-S1 or later
  4. 4. For devices on 21.4 branch: upgrade to 21.4R3 or later
  5. 5. For devices on 22.1 branch: upgrade to 22.1R2 or later
  6. 6. For devices on 22.2 branch: upgrade to 22.2R2 or later
  7. 7. Download the appropriate Junos OS upgrade image from Juniper Networks support portal
  8. 8. Upload the upgrade image to the device using SCP or FTP
Caveat Standard Junos upgrade precautions apply - ensure configuration backup and check for hardware compatibility before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Junos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-30401 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-30401 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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