# CVE-2018-11723: Information disclosure in n/a

> Remote attackers can cause information disclosure via heap-based buffer over-read in libpff by processing crafted PFF files.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **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:** 19 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-11723, GHSA-fjv9-r9p4-38h5

## What is CVE-2018-11723?

CVE-2018-11723 is a medium-severity vulnerability in n/a, published on 19 Jun 2018. 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

The libpff_name_to_id_map_entry_read function in libpff_name_to_id_map.c in libyal libpff through 2018-04-28 allows remote attackers to cause an information disclosure (heap-based buffer over-read) via a crafted pff file. NOTE: the vendor has disputed this as described in libyal/libpff issue 66 on GitHub

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

## Which versions are affected by CVE-2018-11723?

It affects 1 product.


Products: Libpff Project Libpff.

## How do I fix CVE-2018-11723?

No fix published yet.

## Is CVE-2018-11723 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-18897](https://insights.sbomify.com/CVE-2020-18897/): Use after free in n/a (high 7.8)
- [CVE-2018-20348](https://insights.sbomify.com/CVE-2018-20348/): Denial of service in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-11723 and fix it if it is affected.

What it is: CVE-2018-11723 is a medium-severity vulnerability in n/a, published on 19 Jun 2018. 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-2018-11723 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-2018-11723/ (Markdown: https://insights.sbomify.com/CVE-2018-11723/index.md)
```

## Sources

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

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