# CVE-2019-11273: PKS Telemetry logs credentials

> Authenticated users with log access can retrieve billing database credentials from PKS telemetry logs, requiring an upgrade to secure versions.

- **Severity:** Low 2.2 (`CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jul 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-93f7-xvxj-xh3r

## What is CVE-2019-11273?

CVE-2019-11273 is a low-severity vulnerability in Pivotal Container Service (PKS), published on 23 Jul 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Pivotal Container Services (PKS) versions 1.3.x prior to 1.3.7, and versions 1.4.x prior to 1.4.1, contains a vulnerable component which logs the username and password to the billing database. A remote authenticated user with access to those logs may be able to retrieve non-sensitive information.

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

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

It affects 1 product.


Products: Pivotal Software Pivotal Container Service.

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

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

## Is CVE-2019-11273 being exploited?

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

## Other vulnerabilities in Pivotal Container Service (PKS)

- [CVE-2018-15763](https://insights.sbomify.com/CVE-2018-15763/): PKS leaks IaaS Credentials to Application Logs (critical 9.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-11273 is a low-severity vulnerability in Pivotal Container Service (PKS), published on 23 Jul 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-11273 in the wild and no public exploit code.

Affected product: Pivotal Container Service (PKS). 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-11273/ (Markdown: https://insights.sbomify.com/CVE-2019-11273/index.md)
```

## Sources

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

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