Security readout for executives and security teams
Plain-English summary
PKS telemetry could place billing database usernames and passwords in logs. The business risk is limited because an attacker must already be authenticated and able to access those logs, but exposed credentials in logs still weaken internal controls.
Executive priority
Treat as low priority unless affected PKS versions remain in production or log access is broad. Remediation should be scheduled with routine platform maintenance and credential hygiene work.
Technical view
CVE-2019-11273 is CWE-532 information exposure in Pivotal Container Service. A vulnerable component logs billing database username and password values. Affected versions are PKS 1.3.x before 1.3.7 and 1.4.x before 1.4.1. CVSS v3.0 is 2.2 Low.
Likely exposure
Exposure is limited to organizations running the affected legacy PKS versions, especially where authenticated users or operators can read telemetry or billing database logs.
Exploitation context
The source bundle provides no KEV listing and no evidence of active exploitation. The described scenario requires remote authentication, high privileges, and access to relevant logs.
Researcher notes
The CVE text identifies credential logging, but also describes low confidentiality impact and retrieval of non-sensitive information. Do not assume wider secret exposure beyond the cited PKS billing database logging behavior.
Mitigation direction
- Upgrade PKS 1.3.x deployments to 1.3.7 or later.
- Upgrade PKS 1.4.x deployments to 1.4.1 or later.
- Review vendor guidance for any additional remediation details.
- Restrict access to PKS telemetry and billing database logs.
- Rotate exposed billing database credentials if logs may have been accessed.
Validation and detection
- Inventory PKS deployments and record exact versions.
- Confirm no affected 1.3.x or 1.4.x versions remain.
- Review log access permissions for unnecessary authenticated users.
- Check historical logs for billing database credential exposure.
- Verify credential rotation if exposure is found or suspected.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-532: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2019-11273 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 2.2 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:N0.71.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.0 score
2.2LowVector: CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://pivotal.io/security/CVE-2019-11273CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Insertion of Sensitive Information into Log File
Insertion of Sensitive Information into Log File represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.