# CVE-2020-7217: Denial of service in n/a

> Network attackers can cause a denial of service in openSUSE wicked by sending crafted DHCP4 packets with varying client IDs.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-j299-xp2p-5fm9

## What is CVE-2020-7217?

CVE-2020-7217 is a high-severity denial of service vulnerability in n/a, published on 10 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An ni_dhcp4_fsm_process_dhcp4_packet memory leak in openSUSE wicked 0.6.55 and earlier allows network attackers to cause a denial of service by sending DHCP4 packets with a different client-id.

Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime)

## Which versions are affected by CVE-2020-7217?

It affects 1 product.


Products: Opensuse Wicked.

## How do I fix CVE-2020-7217?

Upgrade to a fixed version.

## Is CVE-2020-7217 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-7217 and fix it if it is affected.

What it is: CVE-2020-7217 is a high-severity denial of service vulnerability in n/a, published on 10 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-7217 in the wild and no public exploit code.

Affected product: n/a. 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-2020-7217/ (Markdown: https://insights.sbomify.com/CVE-2020-7217/index.md)
```

## Sources

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

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