# CVE-2022-21711: Out-of-bounds Read lead to application crashes or information leakage in ELF parsing.

> An out-of-bounds read in elfspirit allows attackers to leak memory or crash the application via a crafted ELF file.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Jan 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-jr8h-2657-m68r

## What is CVE-2022-21711?

CVE-2022-21711 is a high-severity vulnerability in liyansong2018 elfspirit, published on 24 Jan 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

elfspirit is an ELF static analysis and injection framework that parses, manipulates, and camouflages ELF files. When analyzing the ELF file format in versions prior to 1.1, there is an out-of-bounds read bug, which can lead to application crashes or information leakage. By constructing a special format ELF file, the information of any address can be leaked. elfspirit version 1.1 contains a patch for this issue.

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

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

It affects 1 product.


Products: Elfspirit Project Elfspirit.

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

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

## Is CVE-2022-21711 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-21711 is a high-severity vulnerability in liyansong2018 elfspirit, published on 24 Jan 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-21711 exists.

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

## Sources

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

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