dbcve.org
JunosOperating system · Juniper

CVE-2025-52960

MEDIUM · 5.9 CVSS v3.1 Published 2025-10-09
Fix available
A fix is available. Upgrade to 22.4 or later.
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
A Buffer Copy without Checking Size of Input vulnerability in the Session Initialization Protocol (SIP) ALG of Juniper Networks Junos OS on MX Series and SRX Series allows an unauthenticated, network-based attacker to cause a Denial of Service (DoS). When memory utilization is high, and specific SIP packets are received, flowd/mspmand crashes. While the system recovers automatically, the disruption can significantly impact service stability. Continuous receipt of these specific SIP packets, while high utilization is present, will cause a sustained DoS condition. The utilization is outside the attackers control, so they would not be able to deterministically exploit this. This issue affects Junos OS on SRX Series and MX Series:  * All versions before 22.4R3-S7, * from 23.2 before 23.2R2-S4, * from 23.4 before 23.4R2-S5, * from 24.2 before 24.2R2.

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

Buffer copy without size check vulnerability in the SIP ALG of Juniper Junos OS on MX/SRX Series. When memory utilization is high and specific SIP packets are received, a buffer overflow causes the flowd/mspmand processes to crash, resulting in denial of service.

MitigationUpgrade Junos OS to 22.4R3-S7, 23.2R2-S4, 23.4R2-S5, or 24.2R2 or later. Consider disabling SIP ALG if not required, and monitor memory utilization.

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:< 22.4= 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
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. Verify device is MX or SRX series
    Run 'show chassis hardware' or check device model via 'show system information'
    Affected if Device is not an MX or SRX series - the vulnerability only affects these platforms
  2. Check installed Junos OS version
    Run 'show version' and compare the version number to affected ranges: 22.4, 23.2, 23.4, 24.2, or any version below 22.4
    Affected if Version matches 22.4, 23.2, 23.4, 24.2, or is below 22.4 - these are the vulnerable versions
  3. Confirm SIP ALG is enabled
    Run 'show security alg sip' to check SIP ALG status
    Affected if SIP ALG is enabled - the buffer overflow only occurs when SIP ALG processes the malicious packets
  4. Check for recent flowd or mspmand process crashes
    Run 'show system processes extensive' and review system logs for recent process crashes using 'show log messages | match flowd|mspmand'
    Affected if Recent crashes of flowd or mspmand processes are present, especially under high memory conditions

Device is affected if it is an MX/SRX series running a vulnerable Junos version (22.4, 23.2, 23.4, 24.2, or below 22.4) with SIP ALG enabled and experiencing process crashes.

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 22.4 or later
Fixed in 22.4
Interim mitigation

Upgrade Junos OS to 22.4R3-S7, 23.2R2-S4, 23.4R2-S5, or 24.2R2 or later. Consider disabling SIP ALG if not required, and monitor memory utilization.

Recommended fix High confidence

22.4R3-S7 or later (22.4 branch), 23.2R2-S4 or later (23.2 branch), 23.4R2-S5 or later (23.4 branch), or 24.2R2 or later

  1. Schedule a maintenance window for the upgrade procedure
  2. Backup the current Junos OS configuration using 'request system configuration rescue save' or equivalent
  3. Download the appropriate fixed Junos OS version for your platform (MX Series or SRX Series): 22.4R3-S7 or later for 22.4 branch, 23.2R2-S4 or later for 23.2 branch, 23.4R2-S5 or later for 23.4 branch, or 24.2R2 or later for 24.2 branch
  4. Upload the new Junos OS image to the device using 'request system software add <package>' or via Web UI
  5. Reboot the device to apply the new software version using 'request system reboot'
  6. After reboot, verify the new version is running using 'show version'
  7. Verify that the SIP ALG is functioning properly and no crashes are occurring
Caveat Review Junos OS release notes for any configuration changes or new features that may affect existing setup; ensure compatibility with other network devices before upgrading

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

Fix this in Junos Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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