dbcve.org
JunosOperating system · Juniper

CVE-2022-22176

MEDIUM · 6.5 CVSS v3.1 Published 2022-01-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
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 Validation of Syntactic Correctness of Input vulnerability in the Juniper DHCP daemon (jdhcpd) of Juniper Networks Junos OS allows an adjacent unauthenticated attacker sending a malformed DHCP packet to cause a crash of jdhcpd and thereby a Denial of Service (DoS). If option-82 is configured in a DHCP snooping / -security scenario, jdhcpd crashes if a specific malformed DHCP request packet is received. The DHCP functionality is impacted while jdhcpd restarts, and continued exploitation of the vulnerability will lead to the unavailability of the DHCP service and thereby a sustained DoS. This issue affects Juniper Networks Junos OS 13.2 version 13.2R1 and later versions prior to 15.1R7-S11; 18.3 versions prior to 18.3R3-S6; 18.4 versions prior to 18.4R2-S9, 18.4R3-S10; 19.1 versions prior to 19.1R2-S3, 19.1R3-S7; 19.2 versions prior to 19.2R1-S8, 19.2R3-S4; 19.3 versions prior to 19.3R2-S7, 19.3R3-S4; 19.4 versions prior to 19.4R3-S6; 20.1 versions prior to 20.1R3-S3; 20.2 versions prior to 20.2R3-S3; 20.3 versions prior to 20.3R3-S1; 20.4 versions prior to 20.4R3; 21.1 versions prior to 21.1R2-S1, 21.1R3; 21.2 versions prior to 21.2R1-S1, 21.2R2. This issue does not affect Juniper Networks Junos OS version 12.3R12 and prior versions.

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 vulnerability in the Juniper DHCP daemon (jdhcpd) of Junos OS allows an adjacent unauthenticated attacker to send a malformed DHCP packet that causes jdhcpd to crash, resulting in denial of service. The crash occurs specifically when option-82 is configured in DHCP snooping or security scenarios. Repeated exploitation can lead to sustained unavailability of DHCP services.

MitigationUpgrade Junos OS to a fixed version (15.1R7-S11, 18.3R3-S6, 18.4R3-S10, 19.1R3-S7, 19.2R3-S4, 19.3R3-S4, 19.4R3-S6, 20.1R3-S3, 20.2R3-S3, 20.3R3-S1, 20.4R3, 21.1R2-S1/21.1R3, or 21.2R1-S1/21.2R2) or later. Alternatively, disable DHCP snooping/security features if not required.

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:= 13.2= 13.2x51= 13.2x52= 13.3= 13.3r9= 14.1= 14.1r7= 14.1x50= 14.1x51= 14.1x53= 14.1x53-d10= 14.1x53-d15

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
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/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. Identify Junos OS version
    Run 'show version' on the device CLI to retrieve the installed Junos OS version
    Affected if The installed version matches any of the affected versions: 13.2, 13.2x51, 13.2x52, 13.3, 13.3r9, 14.1, 14.1r7, 14.1x50, 14.1x51, 14.1x53, 14.1x53-d10, or 14.1x53-d15
  2. Verify DHCP snooping is enabled
    Enter configuration mode and run 'show configuration forwarding-options helpers dhcp-security' or 'show configuration protocols dhcp-security' to see if DHCP security features are configured
    Affected if DHCP snooping or DHCP security is configured with option-82 enabled (the vulnerability triggers specifically when option-82 is in use)
  3. Confirm option-82 configuration in DHCP
    Run 'show configuration | match option-82' or inspect the DHCP security profile configuration for option-82 settings
    Affected if Option-82 is explicitly configured in any DHCP snooping or security scenario
  4. Check jdhcpd process status
    Run 'show system processes extensive | match jdhcpd' or 'request system process check jdhcpd' to verify if the DHCP daemon is running
    Affected if The jdhcpd process is not running or has crashed, indicating possible exploitation

A user is affected if the device runs an affected Junos version AND has DHCP snooping or DHCP security with option-82 configured, or if the jdhcpd process is found to be crashed.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Junos OS to a fixed version (15.1R7-S11, 18.3R3-S6, 18.4R3-S10, 19.1R3-S7, 19.2R3-S4, 19.3R3-S4, 19.4R3-S6, 20.1R3-S3, 20.2R3-S3, 20.3R3-S1, 20.4R3, 21.1R2-S1/21.1R3, or 21.2R1-S1/21.2R2) or later. Alternatively, disable DHCP snooping/security features if not required.

Recommended fix High confidence

Upgrade to the fixed release for your version branch (e.g., 21.2R2 or later if available)

  1. 1. Identify the current Junos OS version running on the device using 'show version'
  2. 2. Determine which version branch you are running (13.2, 18.3, 18.4, 19.1, 19.2, 19.3, 19.4, 20.1, 20.2, 20.3, 20.4, 21.1, or 21.2)
  3. 3. Based on your current branch, plan an upgrade to the first fixed version in that branch: 15.1R7-S11 (for 13.2), 18.3R3-S6 (for 18.3), 18.4R3-S10 (for 18.4), 19.1R3-S7 (for 19.1), 19.2R3-S4 (for 19.2), 19.3R3-S4 (for 19.3), 19.4R3-S6 (for 19.4), 20.1R3-S3 (for 20.1), 20.2R3-S3 (for 20.2), 20.3R3-S1 (for 20.3), 20.4R3 (for 20.4), 21.1R3 (for 21.1), or 21.2R2 (for 21.2)
  4. 4. Download the appropriate Junos OS upgrade package from the Juniper Networks support portal
  5. 5. Upload the software package to the device using 'file copy' or USB storage
  6. 6. Install the upgrade using 'request system software add <package>' with the 'reboot' option
  7. 7. After reboot, verify the new version is running and confirm DHCP service is operational using 'show dhcp server binding'
  8. 8. Test DHCP functionality by verifying clients can obtain addresses
Caveat Major version upgrades may require careful planning; review Juniper upgrade documentation for compatibility and migration steps

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

Fix this in Junos Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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