# CVE-2019-6648: Information disclosure in F5 Container Ingress Service

> Attackers with log access can read sensitive SSL private keys and passphrases if DEBUG logging is enabled in F5 CIS.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Sep 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-jmpc-vpwq-88q3

## What is CVE-2019-6648?

CVE-2019-6648 is a medium-severity vulnerability in Redhat Openshift, published on 4 Sep 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

On version 1.9.0, If DEBUG logging is enable, F5 Container Ingress Service (CIS) for Kubernetes and Red Hat OpenShift (k8s-bigip-ctlr) log files may contain BIG-IP secrets such as SSL Private Keys and Private key Passphrases as provided as inputs by an AS3 Declaration.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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

It affects 2 products.


Products: F5 Container Ingress Service, Redhat Openshift.

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

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

## Is CVE-2019-6648 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-6648 is a medium-severity vulnerability in Redhat Openshift, published on 4 Sep 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-6648 in the wild and no public exploit code.

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

## Sources

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

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