dbcve.org
JunosOperating system · Juniper

CVE-2024-39549

HIGH · 7.5 CVSS v3.1 Published 2024-07-11
Fix available
A fix is available. Upgrade to after 21.1 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
A Missing Release of Memory after Effective Lifetime vulnerability in the routing process daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an attacker to send a malformed BGP Path attribute update which allocates memory used to log the bad path attribute. This memory is not properly freed in all circumstances, leading to a Denial of Service (DoS). Consumed memory can be freed by manually restarting Routing Protocol Daemon (rpd). Memory utilization could be monitored by:  user@host> show system memory or show system monitor memory status This issue affects: Junos OS:  * All versions before 21.2R3-S8,  * from 21.4 before 21.4R3-S8, * from 22.2 before 22.2R3-S4,  * from 22.3 before 22.3R3-S3,  * from 22.4 before 22.4R3-S3, * from 23.2 before 23.2R2-S1,  * from 23.4 before 23.4R1-S2, 23.4R2. Junos OS Evolved: * All versions before 21.2R3-S8-EVO, * from 21.4 before 21.4R3-S8-EVO, * from 22.2 before 22.2R3-S4-EVO, * from 22.3 before 22.3R3-S3-EVO, * from 22.4 before 22.4R3-S3-EVO, * from 23.2 before 23.2R2-S1-EVO, * from 23.4 before 23.4R1-S2-EVO, 23.4R2-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

Memory leak in Juniper rpd daemon where malformed BGP Path attribute updates allocate memory for logging but fail to properly release it in all circumstances, causing memory exhaustion and DoS. The leak occurs specifically in the BGP path attribute logging code path.

MitigationApply Juniper-supplied software updates for affected versions; monitor memory with 'show system memory' or 'show system monitor memory status'; restart rpd as temporary mitigation to free leaked memory.

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.1= 21.2= 21.4= 22.2= 22.3= 22.4= 23.2= 23.4= 24.2
Junos Os EvolvedOperating system
Affected:<= 21.1= 21.2= 21.4= 22.2= 22.3= 22.4= 23.2= 23.4= 24.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. Check Junos version
    Run 'show version' or 'show version detail' to display the installed Junos version
    Affected if The displayed version matches one of the affected versions: 21.1 or earlier, 21.2, 21.4, 22.2, 22.3, 22.4, 23.2, 23.4, or 24.2
  2. Verify BGP is configured
    Run 'show configuration protocols bgp' to check if BGP protocol is configured
    Affected if BGP is actively configured on the device - the vulnerability only applies when BGP is enabled
  3. Confirm rpd daemon is running
    Run 'show system processes routing' or 'ps aux | grep rpd' to verify the rpd process is active
    Affected if The rpd (routing protocol daemon) process is running - this is the component with the memory leak
  4. Monitor rpd memory usage
    Run 'show system memory' and check the memory utilization for the rpd process, or use 'show system monitor memory status' for detailed rpd memory statistics
    Affected if Memory usage for the rpd process is abnormally high or continuously increasing over time, indicating potential memory leak from malformed BGP path attributes

The device is affected if it runs any of the listed affected Junos or Junos OS Evolved versions AND has BGP protocol configured, with rpd showing elevated memory consumption from BGP path attribute logging operations.

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 a release after 21.1
Interim mitigation

Apply Juniper-supplied software updates for affected versions; monitor memory with 'show system memory' or 'show system monitor memory status'; restart rpd as temporary mitigation to free leaked memory.

Recommended fix High confidence

Upgrade to the S-release (e.g., 22.2R3-S4 or 23.4R2) corresponding to your current branch - see Juniper KB for exact version matrix

  1. 1. Identify current Junos OS/Evolved version using: show version
  2. 2. Based on current version branch, identify the minimum fixed S-release from the list: Junos OS: 21.2R3-S8, 21.4R3-S8, 22.2R3-S4, 22.3R3-S3, 22.4R3-S3, 23.2R2-S1, 23.4R1-S2 or 23.4R2 | Junos OS Evolved: 21.2R3-S8-EVO, 21.4R3-S8-EVO, 22.2R3-S4-EVO, 22.3R3-S3-EVO, 22.4R3-S3-EVO, 23.2R2-S1-EVO, 23.4R1-S2-EVO or 23.4R2-EVO
  3. 3. Plan maintenance window as upgrade requires system reboot
  4. 4. Download the appropriate S-release from Juniper support portal
  5. 5. Upload the image to the device using: file copy <source> /var/tmp/
  6. 6. Install the upgrade using: request system software add /var/tmp/<image> reboot
  7. 7. After reboot, verify fixed version: show version
  8. 8. Monitor memory usage: show system memory or show system monitor memory status
Caveat Standard Junos upgrade considerations apply - review Junos upgrade guide for your hardware platform; S-releases are typically minor updates with low risk

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

Fix this in Junos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,320
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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