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

> Local attackers can read sensitive data by pre-creating temporary files that Keepalived overwrites, exposing internal state information.

- **Severity:** Medium 4.7 (`CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Nov 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-19046, GHSA-fjwx-29fr-83hw, UBUNTU-CVE-2018-19046

## What is CVE-2018-19046?

CVE-2018-19046 is a medium-severity vulnerability in n/a, published on 8 Nov 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

keepalived 2.0.8 didn't check for existing plain files when writing data to a temporary file upon a call to PrintData or PrintStats. If a local attacker had previously created a file with the expected name (e.g., /tmp/keepalived.data or /tmp/keepalived.stats), with read access for the attacker and write access for the keepalived process, then this potentially leaked sensitive information.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Keepalived Keepalived.

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

Apply the vendor's patch.

## Is CVE-2018-19046 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-19045](https://insights.sbomify.com/CVE-2018-19045/): Information disclosure in n/a (high 7.5)
- [CVE-2018-19044](https://insights.sbomify.com/CVE-2018-19044/): Path traversal in n/a (medium 4.7)
- [CVE-2011-1784](https://insights.sbomify.com/CVE-2011-1784/): Privilege escalation in n/a (low 3.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-19046 is a medium-severity vulnerability in n/a, published on 8 Nov 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-19046 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-19046/ (Markdown: https://insights.sbomify.com/CVE-2018-19046/index.md)
```

## Sources

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

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