# CVE-2017-15922: Memory corruption in n/a

> An out-of-bounds read in GNU Libextractor allows attackers to cause denial of service or disclose sensitive memory contents via crafted DVI files.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/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:** Yes
- **Published:** 26 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-15922, GHSA-9r4w-4465-whwv, UBUNTU-CVE-2017-15922

## What is CVE-2017-15922?

CVE-2017-15922 is a medium-severity memory corruption vulnerability in n/a, published on 26 Oct 2017. 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

In GNU Libextractor 1.4, there is an out-of-bounds read in the EXTRACTOR_dvi_extract_method function in plugins/dvi_extractor.c.

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

## Which versions are affected by CVE-2017-15922?

It affects 1 product.


Products: Gnu Libextractor.

## How do I fix CVE-2017-15922?

Upgrade to a fixed version.

## Is CVE-2017-15922 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-15600](https://insights.sbomify.com/CVE-2017-15600/): Null dereference in n/a (high 7.5)
- [CVE-2017-15601](https://insights.sbomify.com/CVE-2017-15601/): Memory corruption in n/a (high 7.5)
- [CVE-2017-15602](https://insights.sbomify.com/CVE-2017-15602/): Integer overflow in n/a (high 7.5)
- [CVE-2017-15267](https://insights.sbomify.com/CVE-2017-15267/): Null dereference in n/a (high 7.5)
- [CVE-2017-17440](https://insights.sbomify.com/CVE-2017-17440/): Null dereference in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-15922 and fix it if it is affected.

What it is: CVE-2017-15922 is a medium-severity memory corruption vulnerability in n/a, published on 26 Oct 2017. 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: There is no known exploitation of CVE-2017-15922 in the wild and no public exploit code.

Affected product: n/a. 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-2017-15922/ (Markdown: https://insights.sbomify.com/CVE-2017-15922/index.md)
```

## Sources

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

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