# CVE-2019-3899: Missing authorization in heketi

> Heketi's default configuration lacks authentication, allowing attackers to access the management interface and potentially modify storage configurations.

- **Severity:** High 7.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-g8m6-5j3r-8xg4, RHSA-2019:3255

## What is CVE-2019-3899?

CVE-2019-3899 is a high-severity missing authorization vulnerability in Redhat Openshift Container Platform, published on 22 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

It was found that default configuration of Heketi does not require any authentication potentially exposing the management interface to misuse. This isue only affects heketi as shipped with Openshift Container Platform 3.11.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-592 (DEPRECATED: Authentication Bypass Issues)

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

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `heketi` | Red Hat:storage:3.5:server:el7 | All versions | 0:9.0.0-7.el7rhgs |
| `heketi-client` | Red Hat:storage:3.5:server:el7 | All versions | 0:9.0.0-7.el7rhgs |
| `python-heketi` | Red Hat:storage:3.5:server:el7 | All versions | 0:9.0.0-7.el7rhgs |
| `heketi` | Red Hat:storage:3:client:el7 | All versions | 0:9.0.0-7.el7rhgs |
| `heketi-client` | Red Hat:storage:3:client:el7 | All versions | 0:9.0.0-7.el7rhgs |

Products: Heketi Project Heketi, Redhat Openshift Container Platform.

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

Apply the vendor's patch.

## Is CVE-2019-3899 being exploited?

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

## Other vulnerabilities in Redhat Openshift Container Platform

- [CVE-2017-15103](https://insights.sbomify.com/CVE-2017-15103/): Heketi Arbitrary Code Execution (high 8.8)
- [CVE-2017-15104](https://insights.sbomify.com/CVE-2017-15104/): Information Exposure in Heketi (high 7.8)
- [CVE-2020-10763](https://insights.sbomify.com/CVE-2020-10763/): Heketi logs sensitive information (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-3899 is a high-severity missing authorization vulnerability in Redhat Openshift Container Platform, published on 22 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-3899 in the wild and no public exploit code.

Affected product: Redhat Openshift Container Platform. 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-3899/ (Markdown: https://insights.sbomify.com/CVE-2019-3899/index.md)
```

## Sources

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

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