# CVE-2019-13314: Information disclosure in n/a

> Local attackers can discover root passwords by inspecting process lists, exposing sensitive credentials in virt-bootstrap.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 5 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-xjrr-39hg-vq3j, SUSE-SU-2020:3045-1, openSUSE-SU-2020:1787-1, openSUSE-SU-2020:1856-1

## What is CVE-2019-13314?

CVE-2019-13314 is a high-severity vulnerability in n/a, published on 5 Jul 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

virt-bootstrap 1.1.0 allows local users to discover a root password by listing a process, because this password may be present in the --root-password option to virt_bootstrap.py.

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

## Which versions are affected by CVE-2019-13314?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `virt-bootstrap` | SUSE:Linux Enterprise Module for Server Applications 15 SP1 | All versions | 1.0.0-5.3.124 |
| `virt-bootstrap` | SUSE:Linux Enterprise Module for Server Applications 15 SP2 | All versions | 1.0.0-5.3.124 |
| `virt-bootstrap` | openSUSE:Leap 15.1 | All versions | 1.0.0-lp151.4.3.1 |
| `virt-bootstrap` | openSUSE:Leap 15.2 | All versions | 1.0.0-lp152.5.3.1 |

Products: Redhat Virt-Bootstrap.

## How do I fix CVE-2019-13314?

Apply the vendor's patch.

## Is CVE-2019-13314 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-13314 and fix it if it is affected.

What it is: CVE-2019-13314 is a high-severity vulnerability in n/a, published on 5 Jul 2019. 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-2019-13314 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-2019-13314/ (Markdown: https://insights.sbomify.com/CVE-2019-13314/index.md)
```

## Sources

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

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