# CVE-2020-14156: Misconfiguration in n/a

> OpenBMC IPMI daemon stores passwords with weak file permissions, allowing local attackers to read credentials and potentially escalate privileges.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-q8hw-xhc2-q397

## What is CVE-2020-14156?

CVE-2020-14156 is a high-severity vulnerability in n/a, published on 15 Jun 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

user_channel/passwd_mgr.cpp in OpenBMC phosphor-host-ipmid before 2020-04-03 does not ensure that /etc/ipmi-pass has strong file permissions.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2020-14156?

It affects 1 product.


Products: Openbmc-Project Openbmc.

## How do I fix CVE-2020-14156?

No fix has been published for CVE-2020-14156 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-14156 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-39296](https://insights.sbomify.com/CVE-2021-39296/): Auth bypass in n/a (critical 10.0)
- [CVE-2022-2809](https://insights.sbomify.com/CVE-2022-2809/): Unauthenticated out of bounds heap write in bmcweb (high 8.2)
- [CVE-2022-3409](https://insights.sbomify.com/CVE-2022-3409/): Unauthenticated out of bounds stack write in bmcweb (high 8.2)
- [CVE-2021-39295](https://insights.sbomify.com/CVE-2021-39295/): Denial of service in n/a (high 7.5)
- [CVE-2022-35729](https://insights.sbomify.com/CVE-2022-35729/): Denial of service in OpenBMC (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-14156 and fix it if it is affected.

What it is: CVE-2020-14156 is a high-severity vulnerability in n/a, published on 15 Jun 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-14156 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-2020-14156/ (Markdown: https://insights.sbomify.com/CVE-2020-14156/index.md)
```

## Sources

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

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