# CVE-2022-2881: Buffer overread in statistics channel code

> A buffer overread in BIND9's statistics channel allows attackers to read sensitive memory or crash the service.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Sep 2022
- **Updated:** 28 May 2025
- **Also known as:** ALPINE-CVE-2022-2881, DEBIAN-CVE-2022-2881, GHSA-gjh8-h6gp-pqgr, ROOT-OS-DEBIAN-11-CVE-2022-2881, UBUNTU-CVE-2022-2881

## What is CVE-2022-2881?

CVE-2022-2881 is a medium-severity vulnerability in Isc Bind, published on 21 Sep 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The underlying bug might cause read past end of the buffer and either read memory it should not read, or crash the process.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Isc Bind.

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

Apply the vendor's patch.

## Is CVE-2022-2881 being exploited?

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

## Other vulnerabilities in Isc Bind

- [CVE-2008-0122](https://insights.sbomify.com/CVE-2008-0122/): Memory corruption in n/a (critical 10.0)
- [CVE-2001-0010](https://insights.sbomify.com/CVE-2001-0010/): Memory corruption in n/a (critical 10.0)
- [CVE-2001-0011](https://insights.sbomify.com/CVE-2001-0011/): Memory corruption in n/a (critical 10.0)
- [CVE-2001-0013](https://insights.sbomify.com/CVE-2001-0013/): Memory corruption in n/a (critical 10.0)
- [CVE-2000-1029](https://insights.sbomify.com/CVE-2000-1029/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-2881 is a medium-severity vulnerability in Isc Bind, published on 21 Sep 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-2881 in the wild and no public exploit code.

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

## Sources

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

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