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

> A heap-based buffer over-read in liblnk allows remote attackers to disclose sensitive information via a crafted lnk file.

- **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-12098, GHSA-x4qr-xrm4-qp2m, UBUNTU-CVE-2018-12098

## What is CVE-2018-12098?

CVE-2018-12098 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 liblnk_data_block_read function in liblnk_data_block.c in liblnk through 2018-04-19 allows remote attackers to cause an information disclosure (heap-based buffer over-read) via a crafted lnk file. NOTE: the vendor has disputed this as described in libyal/liblnk issue 33 on GitHub

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Liblnk Project Liblnk.

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

No fix published yet.

## Is CVE-2018-12098 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-12096](https://insights.sbomify.com/CVE-2018-12096/): Information disclosure in n/a (medium 5.5)
- [CVE-2018-12097](https://insights.sbomify.com/CVE-2018-12097/): Information disclosure in n/a (medium 5.5)
- [CVE-2019-17401](https://insights.sbomify.com/CVE-2019-17401/): Memory corruption in n/a (low 3.3)
- [CVE-2019-17264](https://insights.sbomify.com/CVE-2019-17264/): Memory corruption in n/a (low 3.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-12098 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-12098 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-12098/ (Markdown: https://insights.sbomify.com/CVE-2018-12098/index.md)
```

## Sources

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

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