dbcve.org
JunosOperating system · Juniper

CVE-2025-30648

HIGH · 7.4 CVSS v3.1 Published 2025-04-09
Fix available
A fix is available. Upgrade to 21.2 or later.
See remediation →
79/100
Remediation priority · High
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 Improper Input Validation vulnerability in the Juniper DHCP Daemon (jdhcpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, adjacent attacker to cause the jdhcpd process to crash resulting in a Denial of Service (DoS). When a specifically malformed DHCP packet is received from a DHCP client, the jdhcpd process crashes, which will lead to the unavailability of the DHCP service and thereby resulting in a sustained DoS. The DHCP process will restart automatically to recover the service. This issue will occur when dhcp-security is enabled.  This issue affects Junos OS:  * All versions before 21.2R3-S9,  * from 21.4 before 21.4R3-S10,  * from 22.2 before 22.2R3-S6,  * from 22.4 before 22.4R3-S6,  * from 23.2 before 23.2R2-S3,  * from 23.4 before 23.4R2-S4,  * from 24.2 before 24.2R2;  Junos OS Evolved:  * from 22.4 before 22.4R3-S6-EVO,  * from 23.2 before 23.2R2-S3-EVO,  * from 23.4 before 23.4R2-S4-EVO,  * from 24.2 before 24.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

Improper input validation in Juniper DHCP Daemon (jdhcpd) allows an unauthenticated, adjacent attacker to send a specifically malformed DHCP packet when dhcp-security is enabled, causing the jdhcpd process to crash and resulting in Denial of Service. The process auto-restarts but causes service interruption.

MitigationUpgrade to a fixed Junos OS or Junos OS Evolved version as listed in the advisory (21.2R3-S9, 21.4R3-S10, 22.2R3-S6, 22.4R3-S6, 23.2R2-S3, 23.4R2-S4, 24.2R2 or later). If immediate upgrade is not possible, consider disabling dhcp-security as a temporary workaround if business requirements permit.

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
Junos Os EvolvedOperating system
Affected:= 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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/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 the installed Junos version
    Run 'show version' or 'show version detail' to obtain the exact Junos OS or Junos OS Evolved version installed on the device
    Affected if The installed version matches one of the affected versions listed: Junos < 21.2, = 21.2, = 21.4, = 22.2, = 22.4, = 23.2, = 23.4, = 24.2, or Junos OS Evolved = 22.4, = 23.2, = 23.4, = 24.2
  2. Determine if dhcp-security is enabled
    Examine the DHCP security configuration by running 'show configuration | display set | match dhcp-security' or by reviewing the DHCP security configuration hierarchy under 'set system services dhcp-security'
    Affected if dhcp-security is configured and enabled on the device
  3. Verify the jdhcpd process is running
    Check the status of the jdhcpd process using 'show system processes extensive | match jdhcpd' or similar process status command
    Affected if The jdhcpd process is running and dhcp-security is enabled on a vulnerable version

A device is affected only if it runs a vulnerable Junos or Junos OS Evolved version AND has dhcp-security enabled, allowing an adjacent attacker to crash the jdhcpd process via malformed DHCP packets.

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 a fixed Junos OS or Junos OS Evolved version as listed in the advisory (21.2R3-S9, 21.4R3-S10, 22.2R3-S6, 22.4R3-S6, 23.2R2-S3, 23.4R2-S4, 24.2R2 or later). If immediate upgrade is not possible, consider disabling dhcp-security as a temporary workaround if business requirements permit.

Recommended fix High confidence

Junos OS: Upgrade to 21.2R3-S9 / 21.4R3-S10 / 22.2R3-S6 / 22.4R3-S6 / 23.2R2-S3 / 23.4R2-S4 / 24.2R2 (depending on your current branch); Junos OS Evolved: Upgrade to 22.4R3-S6-EVO / 23.2R2-S3-EVO / 23.4R2-S4-EVO / 24.2R2-EVO

  1. 1. Identify the current Junos OS or Junos OS Evolved version running on the device using 'show version'
  2. 2. Determine which release branch you are on (e.g., 21.2, 21.4, 22.2, 22.4, 23.2, 23.4, 24.2)
  3. 3. Download the appropriate fixed version for your branch from the Juniper support portal
  4. 4. Upload the Junos upgrade package to the device
  5. 5. Install the upgrade using 'request system software add <package>' command
  6. 6. Reboot the device using 'request system reboot' to apply the changes
  7. 7. After reboot, verify the new version is running with 'show version' and confirm DHCP service is operational
Caveat Standard Junos upgrade - review release notes for any changes; this is a maintenance upgrade with no expected breaking changes

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
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
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,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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