# CVE-2022-22707: Memory corruption in n/a

> A stack-based buffer overflow in lighttpd's mod_extforward plugin allows remote attackers to cause a denial of service via crafted Forwarded headers.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/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:** 6 Jan 2022
- **Updated:** 3 Aug 2024
- **Also known as:** ALPINE-CVE-2022-22707, DEBIAN-CVE-2022-22707, DSA-5040-1, GHSA-j3jp-95wp-9q83, MGASA-2022-0161, OESA-2022-1491, UBUNTU-CVE-2022-22707, openSUSE-SU-2022:0024-1, openSUSE-SU-2024:11764-1

## What is CVE-2022-22707?

CVE-2022-22707 is a medium-severity memory corruption vulnerability in Debian Debian Linux, published on 6 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In lighttpd 1.4.46 through 1.4.63, the mod_extforward_Forwarded function of the mod_extforward plugin has a stack-based buffer overflow (4 bytes representing -1), as demonstrated by remote denial of service (daemon crash) in a non-default configuration. The non-default configuration requires handling of the Forwarded header in a somewhat unusual manner. Also, a 32-bit system is much more likely to be affected than a 64-bit system.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `lighttpd` | SUSE:Package Hub 15 SP3 | All versions | 1.4.64-bp153.2.3.1 |
| `lighttpd` | openSUSE:Leap 15.3 | All versions | 1.4.64-bp153.2.3.1 |
| `lighttpd` | openSUSE:Tumbleweed | All versions | 1.4.64-1.1 |

Products: Debian Debian Linux, Lighttpd Lighttpd.

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

Upgrade to a fixed version.

## Is CVE-2022-22707 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-22707 is a medium-severity memory corruption vulnerability in Debian Debian Linux, published on 6 Jan 2022. 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-2022-22707 in the wild and no public exploit code.

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

## Sources

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

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