# CVE-2022-22179: Junos OS: jdhcpd crashes upon receiving a specific DHCP packet

> An adjacent attacker can crash the Junos OS DHCP daemon by sending a specific DHCPv4 packet, causing a denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jan 2022
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-x9v8-cw49-c7pf

## What is CVE-2022-22179?

CVE-2022-22179 is a medium-severity denial of service vulnerability in Juniper Junos, published on 19 Jan 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2022-22179?

It affects 1 product.


Products: Juniper Junos.

## How do I fix CVE-2022-22179?

No fix has been published for CVE-2022-22179 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-22179 being exploited?

There is no known exploitation of CVE-2022-22179 in the wild and no public exploit code.

## Other vulnerabilities in Juniper Junos

- [CVE-2023-36845](https://insights.sbomify.com/CVE-2023-36845/): Juniper Junos OS EX Series and SRX Series PHP External Variable Modification (critical 9.8, exploited in the wild)
- [CVE-2020-1631](https://insights.sbomify.com/CVE-2020-1631/): Juniper Junos OS Path Traversal (high 8.8, exploited in the wild)
- [CVE-2025-21590](https://insights.sbomify.com/CVE-2025-21590/): Juniper Junos OS Improper Isolation or Compartmentalization (medium 6.7, exploited in the wild)
- [CVE-2023-36851](https://insights.sbomify.com/CVE-2023-36851/): Juniper Junos OS SRX Series Missing Authentication for Critical Function (medium 5.3, exploited in the wild)
- [CVE-2023-36844](https://insights.sbomify.com/CVE-2023-36844/): Juniper Junos OS EX Series PHP External Variable Modification (medium 5.3, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-22179 and fix it if it is affected.

What it is: CVE-2022-22179 is a medium-severity denial of service vulnerability in Juniper Junos, published on 19 Jan 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-22179 in the wild and no public exploit code.

Affected product: Juniper Junos. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-22179/ (Markdown: https://insights.sbomify.com/CVE-2022-22179/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-22179
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-22179
- OSV: https://osv.dev/vulnerability/CVE-2022-22179

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-22179/
Summaries are generated and may contain mistakes; the official description above is the record.