# CVE-2022-23093: Stack overflow in ping(8)

> A remote attacker can cause a stack buffer overflow in the FreeBSD ping utility, leading to a denial of service crash.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Feb 2024
- **Updated:** 28 Oct 2024
- **Also known as:** GHSA-7p28-5p54-rq49

## What is CVE-2022-23093?

CVE-2022-23093 is a medium-severity memory corruption vulnerability in Freebsd Freebsd, published on 15 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ping reads raw IP packets from the network to process responses in the pr_pack() function.  As part of processing a response ping has to reconstruct the IP header, the ICMP header and if present a "quoted packet," which represents the packet that generated an ICMP error.  The quoted packet again has an IP header and an ICMP header.

The pr_pack() copies received IP and ICMP headers into stack buffers for further processing.  In so doing, it fails to take into account the possible presence of IP option headers following the IP header in either the response or the quoted packet.  When IP options are present, pr_pack() overflows the destination buffer by up to 40 bytes.

The memory safety bugs described above can be triggered by a remote host, causing the ping program to crash.

The ping process runs in a capability mode sandbox on all affected versions of FreeBSD and is thus very constrained in how it can interact with the rest of the system at the point where the bug can occur.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


Products: Freebsd Freebsd.

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

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

## Is CVE-2022-23093 being exploited?

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

Public exploit code:

- The FreeBSD ICMP buffer overflow, freebsd buffer overflow poc (github_poc): https://github.com/sh4den/CVE-2022-23093
- CVE-2022-23093 FreeBSD Stack-Based Overflow (github_poc): https://github.com/Symbolexe/DrayTek-Exploit

## Other vulnerabilities in Freebsd Freebsd

- [CVE-2018-17160](https://insights.sbomify.com/CVE-2018-17160/): Memory corruption in FreeBSD (critical 10.0)
- [CVE-2014-3954](https://insights.sbomify.com/CVE-2014-3954/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-4304](https://insights.sbomify.com/CVE-2006-4304/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-0226](https://insights.sbomify.com/CVE-2006-0226/): Integer overflow in n/a (critical 10.0)
- [CVE-2004-0002](https://insights.sbomify.com/CVE-2004-0002/): Denial of service in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-23093 is a medium-severity memory corruption vulnerability in Freebsd Freebsd, published on 15 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-23093 in the wild and no public exploit code.

Affected product: Freebsd Freebsd. 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-23093/ (Markdown: https://insights.sbomify.com/CVE-2022-23093/index.md)
```

## Sources

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

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