dbcve.org
JunosOperating system · Juniper

CVE-2022-22163

MEDIUM · 6.5 CVSS v3.1 Published 2022-01-19
Fix available
A fix is available. Upgrade to 15.1 or later.
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 Input Validation vulnerability in the Juniper DHCP daemon (jdhcpd) of Juniper Networks Junos OS allows an adjacent unauthenticated attacker to cause a crash of jdhcpd and thereby a Denial of Service (DoS). If a device is configured as DHCPv6 local server and persistent storage is enabled, jdhcpd will crash when receiving a specific DHCPv6 message. This issue affects: Juniper Networks Junos OS All versions prior to 15.1R7-S11; 18.4 versions prior to 18.4R3-S9; 19.1 versions prior to 19.1R2-S3, 19.1R3-S7; 19.2 versions prior to 19.2R1-S8, 19.2R3-S3; 19.4 versions prior to 19.4R3-S5; 20.1 versions prior to 20.1R3-S1; 20.2 versions prior to 20.2R3-S2; 20.3 versions prior to 20.3R3-S1; 20.4 versions prior to 20.4R3; 21.1 versions prior to 21.1R2; 21.2 versions prior to 21.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

Improper input validation in the Juniper DHCP daemon (jdhcpd) allows an adjacent unauthenticated attacker to crash the service by sending a specific DHCPv6 message. The vulnerability is only exploitable when the device is configured as a DHCPv6 local server with persistent storage enabled, leading to denial of service.

MitigationApply the vendor-supplied patches for affected Junos OS versions, or temporarily mitigate by disabling DHCPv6 local server functionality or persistent storage 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:< 15.1= 15.1= 18.4= 19.1= 19.2= 19.4= 20.1= 20.2= 20.3= 20.4= 21.1= 21.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
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` or `show version detail` on the device and note the installed Junos version.
    Affected if The installed version matches any of these: < 15.1, = 15.1, = 18.4, = 19.1, = 19.2, = 19.4, = 20.1, = 20.2, = 20.3, = 20.4, = 21.1, = 21.2
  2. Verify DHCPv6 local server is configured
    Run `show configuration protocols dhcpv6 local-server` or `show configuration | display set | match dhcpv6` to see if the device is configured as a DHCPv6 local server.
    Affected if The output shows DHCPv6 local-server configuration is present and active on the device.
  3. Confirm persistent storage is enabled for DHCPv6
    Run `show configuration protocols dhcpv6 local-server persistent-storage` or inspect the DHCPv6 local-server configuration for the persistent-storage statement.
    Affected if The configuration includes the persistent-storage option under DHCPv6 local-server.

The device is affected only if it runs an affected Junos version AND has DHCPv6 local-server configured AND has persistent storage enabled; all three conditions must be true for the vulnerability to be exploitable.

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

Apply the vendor-supplied patches for affected Junos OS versions, or temporarily mitigate by disabling DHCPv6 local server functionality or persistent storage if not required.

Recommended fix High confidence

Upgrade to the fixed release for your specific version branch (e.g., 18.4R3-S9, 19.1R3-S7, 20.1R3-S1, etc.) as listed in the Juniper KB article

  1. 1. Identify the current Junos OS version running on the device using 'show version'
  2. 2. Determine the appropriate upgrade path based on the current version branch (15.1, 18.4, 19.1, 19.2, 19.4, 20.1, 20.2, 20.3, 20.4, 21.1, or 21.2)
  3. 3. Download the corresponding fixed release from the Juniper Networks support portal: 15.1R7-S11 or later for 15.1 branch; 18.4R3-S9 or later for 18.4 branch; 19.1R3-S7 or later for 19.1 branch; 19.2R3-S3 or later for 19.2 branch; 19.4R3-S5 or later for 19.4 branch; 20.1R3-S1 or later for 20.1 branch; 20.2R3-S2 or later for 20.2 branch; 20.3R3-S1 or later for 20.3 branch; 20.4R3 or later for 20.4
  4. 4. Upload the Junos OS upgrade package to the device
  5. 5. Reboot the device to apply the upgrade using 'request system reboot'
  6. 6. Verify the new version is running with 'show version' and confirm the DHCP daemon is operational
Caveat Standard Junos OS upgrade considerations apply; verify hardware compatibility and review release notes for any behavioral changes in your version path

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 the upgrade done

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-22163 — 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-22163 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