JunosOperating system · Juniper

CVE-2022-22179

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

NVD · unedited

A Improper Validation of Specified Index, Position, or Offset in Input 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). In a scenario where DHCP relay or local server is configured the problem can be triggered if a DHCPv4 packet with specific options is received leading to a corruption of the options read from the packet. This corruption can then lead to jdhcpd crash and restart. This issue affects: Juniper Networks Junos OS 17.4R1 and later versions prior to 18.4R3-S10; 19.1 versions prior to 19.1R3-S7; 19.2 versions prior to 19.2R1-S8, 19.2R3-S4; 19.3 versions prior to 19.3R3-S4; 19.4 versions prior to 19.4R3-S6; 20.1 versions prior to 20.1R3-S2; 20.2 versions prior to 20.2R3-S3; 20.3 versions prior to 20.3R3-S2; 20.4 versions prior to 20.4R3-S1; 21.1 versions prior to 21.1R2-S2, 21.1R3; 21.2 versions prior to 21.2R1-S2, 21.2R2, 21.2R3; 21.3 versions prior to 21.3R1-S1, 21.3R2.

Technical summary

dbcve analysis · high confidence

A vulnerability in Juniper Networks Junos OS DHCP daemon (jdhcpd) allows an adjacent unauthenticated attacker to cause a denial of service by sending specially crafted DHCPv4 packets with specific options. The improper validation of specified index/offset in input leads to corruption of packet options read, causing jdhcpd to crash and restart.

MitigationApply the appropriate Junos OS security update from Juniper Networks that addresses this vulnerability in the jdhcpd component. Until patched, monitor DHCP relay/server functionality for unexpected restarts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

JunosOperating system

Affected:= 17.4= 18.1= 18.2= 18.3= 18.4= 19.1= 19.2= 19.3= 19.4= 20.1= 20.2= 20.3

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify Junos OS version

Run 'show version' or 'show version detail' on the device and note the exact software version string

Affected if The installed version matches one of these: 17.4, 18.1, 18.2, 18.3, 18.4, 19.1, 19.2, 19.3, 19.4, 20.1, 20.2, or 20.3
Verify DHCP relay or server is configured

Run 'show configuration | display json | match dhcp' or review the configuration for dhcp-relay or dhcp-server sections under [edit services]

Affected if DHCP relay or DHCP server services are configured and active on the device
Confirm jdhcpd process is running

Run 'show system processes | match jdhcpd' or check process status via 'request system process daemon jdhcpd'

Affected if The jdhcpd daemon process is actively running on the device
Check DHCP service restart history

Run 'show system processes restart-history' or review system logs for jdhcpd crash events using 'show log messages | match jdhcpd'

Affected if There are recent unexpected jdhcpd restarts or crash indications in logs

A device is affected if it runs a matching Junos version (17.4 through 20.3) AND has DHCP relay or server functionality enabled, exposing the jdhcpd daemon to specially crafted DHCPv4 packets from an adjacent attacker.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Apply the appropriate Junos OS security update from Juniper Networks that addresses this vulnerability in the jdhcpd component. Until patched, monitor DHCP relay/server functionality for unexpected restarts.

Recommended fix High confidence

Upgrade to Junos OS 21.3R2 or later (or the latest available release). For branch-specific fixes: 18.4R3-S10, 19.1R3-S7, 19.2R3-S4, 19.3R3-S4, 19.4R3-S6, 20.1R3-S2, 20.2R3-S3, 20.3R3-S2, or 20.4R3-S1.

1. Identify the current Junos OS version running on the device using 'show version'
2. Review the DHCP relay or DHCP server configuration using 'show configuration | display set | match dhcp'
3. Download the appropriate fixed Junos OS release from the Juniper Networks website (21.3R2 or later, or the equivalent fixed release for your branch: 18.4R3-S10, 19.1R3-S7, 19.2R3-S4, 19.3R3-S4, 19.4R3-S6, 20.1R3-S2, 20.2R3-S3, 20.3R3-S2, or 20.4R3-S1)
4. Upload the Junos OS upgrade package to the device via FTP/SCP to /var/tmp/
5. Initiate the software install using 'request system software add /var/tmp/<package-name>'
6. Reboot the device using 'request system reboot'
7. After reboot, verify the new version is installed using 'show version'
8. Verify DHCP service is operational using 'show dhcp server binding' or 'show dhcp relay statistics'

Caveat Standard Junos OS upgrade - review release notes for any known issues; standard Junos upgrade best practices apply (backup configuration, test in lab first).

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 / QA2.0 h

20.0 hours of engineering $3,500

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

kb.juniper.netVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-22179 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2022-22179?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 6.5 Medium

Exploit likelihood EPSS, next 30 days 0.4%

Affects: Junos

Remediation

Need this fixed?

Fix this in Junos 20 hrs · Moderate

Typical engagement from $3,500

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2022-22179 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References