# CVE-2022-28711: Memory corruption in APWeb

> A memory corruption flaw in ArduPilot APWeb allows remote attackers to execute arbitrary code or cause denial of service via crafted HTTP requests.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Apr 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-g969-j9qm-fx8r

## What is CVE-2022-28711?

CVE-2022-28711 is a medium-severity memory corruption vulnerability in ArduPilot APWeb, published on 14 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A memory corruption vulnerability exists in the cgi.c unescape functionality of ArduPilot APWeb master branch 50b6b7ac - master branch 46177cb9. A specially-crafted HTTP request can lead to memory corruption. An attacker can send a network request to trigger this vulnerability.

Weakness: CWE-787 (Out-of-bounds Write), CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Ardupilot Apweb.

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

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

## Is CVE-2022-28711 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-28711 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2022-28711 is a medium-severity memory corruption vulnerability in ArduPilot APWeb, published on 14 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-28711 exists.

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

## Sources

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

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