dbcve.org
Junos Os EvolvedOperating system · Juniper

CVE-2024-39548

HIGH · 7.5 CVSS v3.1 Published 2024-07-11
Fix available
A fix is available. Upgrade to 21.2 or later.
See remediation →
84/100
Remediation priority · High
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 Uncontrolled Resource Consumption vulnerability in the aftmand process of Juniper Networks Junos OS Evolved allows an unauthenticated, network-based attacker to consume memory resources, resulting in a Denial of Service (DoS) condition. The processes do not recover on their own and must be manually restarted. This issue affects both IPv4 and IPv6.  Changes in memory usage can be monitored using the following CLI command: user@device> show system memory node <fpc slot> | grep evo-aftmann This issue affects Junos OS Evolved:  * All versions before 21.2R3-S8-EVO,  * 21.3 versions before 21.3R3-S5-EVO,  * 21.4 versions before 21.4R3-S5-EVO,  * 22.1 versions before 22.1R3-S4-EVO,  * 22.2 versions before 22.2R3-S4-EVO, * 22.3 versions before 22.3R3-S3-EVO, * 22.4 versions before 22.4R2-S2-EVO, 22.4R3-EVO,  * 23.2 versions before 23.2R1-S1-EVO, 23.2R2-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 confidence

An unauthenticated network attacker can exploit an uncontrolled resource consumption vulnerability in the aftmand process of Juniper Networks Junos OS Evolved, causing excessive memory consumption that leads to denial of service. The vulnerable process does not self-recover and requires manual restart. Both IPv4 and IPv6 traffic are affected.

MitigationUpgrade to the fixed Junos OS Evolved versions specified in the advisory. As a temporary workaround, monitor memory usage using 'show system memory node <fpc slot> | grep evo-aftmann' and manually restart the process if exhaustion occurs.

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
Junos Os EvolvedOperating system
Affected:< 21.2= 21.2= 21.3= 21.4= 22.1= 22.2= 22.3= 22.4= 23.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
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 checks

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

  1. Confirm Junos OS Evolved is running
    Run 'show version' and look for 'Junos OS Evolved' in the output. This vulnerability only affects Junos OS Evolved, not regular Junos OS.
    Affected if The device is running Junos OS Evolved (not regular Junos OS)
  2. Check installed version against affected ranges
    Run 'show version' and note the exact version number (e.g., 22.3R3-S2). Compare against the affected versions: all versions before 21.2, and versions 21.2, 21.3, 21.4, 22.1, 22.2, 22.3, 22.4, 23.2.
    Affected if The installed version is 21.2, 21.3, 21.4, 22.1, 22.2, 22.3, 22.4, or 23.2, or any version before 21.2
  3. Verify aftmand process is running
    Run 'show system processes' or 'ps -aux | grep aftmand' to confirm the aftmand process is active.
    Affected if The aftmand process is running on the device
  4. Monitor aftmand memory consumption
    Run 'show system memory node <fpc slot> | grep evo-aftmann' to check memory usage of the aftmand process. Alternatively, use 'show system processes extensive | match aftmann'.
    Affected if Memory usage for aftmand is excessively high or continuously growing

If the device runs Junos OS Evolved versions 21.2 through 23.2 (or earlier) and shows high/uncontrolled memory consumption in the aftmand process, the environment is affected by this CVE.

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
Upgrade available Upgrade to 21.2 or later
Fixed in 21.2
Interim mitigation

Upgrade to the fixed Junos OS Evolved versions specified in the advisory. As a temporary workaround, monitor memory usage using 'show system memory node <fpc slot> | grep evo-aftmann' and manually restart the process if exhaustion occurs.

Recommended fix High confidence

Upgrade to one of the fixed releases: 21.2R3-S8-EVO, 21.3R3-S5-EVO, 21.4R3-S5-EVO, 22.1R3-S4-EVO, 22.2R3-S4-EVO, 22.3R3-S3-EVO, 22.4R2-S2-EVO, 22.4R3-EVO, 23.2R1-S1-EVO, or 23.2R2-EVO (or later)

  1. 1. Identify the current Junos OS Evolved version by running: show version
  2. 2. Determine the appropriate upgrade path based on current version and the fixed releases (21.2R3-S8-EVO, 21.3R3-S5-EVO, 21.4R3-S5-EVO, 22.1R3-S4-EVO, 22.2R3-S4-EVO, 22.3R3-S3-EVO, 22.4R2-S2-EVO/22.4R3-EVO, 23.2R1-S1-EVO/23.2R2-EVO)
  3. 3. Back up the current configuration using: request system configuration rescue save
  4. 4. Schedule a maintenance window for the upgrade
  5. 5. Download the appropriate fixed Junos OS Evolved image from supportportal.juniper.net
  6. 6. Upgrade the device using: request system software add <path-to-package> reboot
  7. 7. After reboot, verify the new version: show version
  8. 8. Verify the aftmand process is running properly and monitor memory: show system memory node <fpc slot> | grep evo-aftmann
Caveat Standard Junos OS upgrade precautions apply - ensure configuration compatibility and plan for downtime

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

Fix this in Junos Os Evolved Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,950
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-39548 — 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-39548 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