dbcve.org
JunosOperating system · Juniper

CVE-2025-30658

HIGH · 7.5 CVSS v3.1 Published 2025-04-09
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
A Missing Release of Memory after Effective Lifetime vulnerability in the Anti-Virus processing of Juniper Networks Junos OS on SRX Series allows an unauthenticated, network-based attacker to cause a Denial-of-Service (DoS). On all SRX platforms with Anti-Virus enabled, if a server sends specific content in the HTTP body of a response to a client request, these packets are queued by Anti-Virus processing in Juniper Buffers (jbufs) which are never released. When these jbufs are exhausted, the device stops forwarding all transit traffic. A jbuf memory leak can be noticed from the following logs: (<node>.)<fpc> Warning: jbuf pool id <#> utilization level (<current level>%) is above <threshold>%! To recover from this issue, the affected device needs to be manually rebooted to free the leaked jbufs. This issue affects Junos OS on SRX Series:  * all versions before 21.2R3-S9, * 21.4 versions before 21.4R3-S10, * 22.2 versions before 22.2R3-S6, * 22.4 versions before 22.4R3-S6, * 23.2 versions before 23.2R2-S3, * 23.4 versions before 23.4R2-S3, * 24.2 versions 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

A memory leak vulnerability in the Anti-Virus processing of Juniper Junos OS on SRX Series causes unauthenticated network-based attackers to trigger DoS. When Anti-Virus is enabled and a server sends specific content in HTTP response bodies, packets get queued in Juniper Buffers (jbufs) that are never released, eventually exhausting the buffer pool and stopping all transit traffic.

MitigationUpgrade Junos OS to a fixed version (21.2R3-S9, 21.4R3-S10, 22.2R3-S6, 22.4R3-S6, 23.2R2-S3, 23.4R2-S3, or 24.2R2 or later). If immediate patching is not feasible, consider disabling Anti-Virus feature as a temporary workaround.

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.2= 21.4= 22.2= 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. Confirm device is SRX Series
    Run 'show chassis hardware' or 'show system hardware' and verify the model is from the SRX product line (e.g., SRX340, SRX550, SRX5800, etc.)
    Affected if Device is NOT an SRX Series - the vulnerability only affects SRX devices
  2. Check installed Junos OS version
    Run 'show version' and note the Junos OS version number (e.g., 21.2, 21.4R1, 22.2, etc.)
    Affected if Version matches any of these: any release before 21.2, or exactly 21.2, 21.4, 22.2, 22.4, 23.2, 23.4, or 24.2 (note: versions with suffixes like 21.2R3-S9 are fixed)
  3. Verify Anti-Virus feature is enabled
    Run 'show security utm anti-virus status' or 'show configuration security utm anti-virus' to check if Anti-Virus policy is configured and active
    Affected if Anti-Virus is NOT enabled - the vulnerability only triggers when Anti-Virus processing is active

If the device is SRX Series, runs an affected Junos version (any before 21.2R3-S9/21.4R3-S10/22.2R3-S6/22.4R3-S6/23.2R2-S3/23.4R2-S3/24.2R2), and has Anti-Virus enabled, the environment is affected by this vulnerability.

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 Junos OS to a fixed version (21.2R3-S9, 21.4R3-S10, 22.2R3-S6, 22.4R3-S6, 23.2R2-S3, 23.4R2-S3, or 24.2R2 or later). If immediate patching is not feasible, consider disabling Anti-Virus feature as a temporary workaround.

Recommended fix High confidence

21.2R3-S9, 21.4R3-S10, 22.2R3-S6, 22.4R3-S6, 23.2R2-S3, 23.4R2-S3, or 24.2R2 (depending on current branch)

  1. 1. Identify the current Junos OS version on the SRX device using 'show version' command
  2. 2. Determine if Anti-Virus (AV) feature is enabled using 'show security antivirus status' command
  3. 3. If AV is enabled, plan an upgrade to a fixed release as the primary remediation
  4. 4. For Junos 21.2 branch: upgrade to 21.2R3-S9 or later
  5. 5. For Junos 21.4 branch: upgrade to 21.4R3-S10 or later
  6. 6. For Junos 22.2 branch: upgrade to 22.2R3-S6 or later
  7. 7. For Junos 22.4 branch: upgrade to 22.4R3-S6 or later
  8. 8. For Junos 23.2 branch: upgrade to 23.2R2-S3 or later
Caveat Standard Junos upgrade considerations apply - review release notes for your specific version transition for any configuration changes or compatibility notes

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 / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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