dbcve.org
Pivotal Software MysqlDatabase / datastore · VMware

CVE-2016-0898

CRITICAL · 10.0 CVSS v3.1 Published 2018-03-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
MySQL for PCF tiles 1.7.x before 1.7.10 were discovered to log the AWS access key in plaintext. These credentials were logged to the Service Backup component logs, and not the system log, thus were not exposed outside the Service Backup VM.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

MySQL for PCF tiles versions 1.7.x before 1.7.10 contained a logging flaw that wrote AWS access keys in plaintext to Service Backup component logs. While the description states these logs were confined to the Service Backup VM and not exposed externally, the CVSS 10 rating indicates the severity of exposed AWS credentials that could be recovered from the VM.

MitigationUpgrade MySQL for PCF tiles to version 1.7.10 or later to resolve the plaintext credential logging. As a precaution, rotate any AWS access keys that may have been logged since the vulnerability could still be exploited if an attacker gains access to the Service Backup VM.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Pivotal Software MysqlDatabase / datastore
Affected:= 1.7.0= 1.7.0.1= 1.7.0.2= 1.7.0.3= 1.7.0.4= 1.7.1= 1.7.2= 1.7.3= 1.7.4= 1.7.5= 1.7.6= 1.7.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check MySQL for PCF tile version
    In Pivotal Ops Manager, navigate to the Installation Dashboard and locate the MySQL for PCF tile. Click on the tile and view the version information typically displayed in the product details or metadata section.
    Affected if The installed version is 1.7.0, 1.7.0.1, 1.7.0.2, 1.7.0.3, 1.7.0.4, 1.7.1, 1.7.2, 1.7.3, 1.7.4, 1.7.5, 1.7.6, or 1.7.7
  2. Verify Service Backup component is enabled
    In Ops Manager, examine the MySQL for PCF tile configuration. Navigate to the Service Backup settings pane and confirm whether the Service Backup job or errand is configured and enabled.
    Affected if Service Backup is enabled and the tile version is in the affected 1.7.x range before 1.7.10
  3. Inspect Service Backup logs for AWS credentials
    Access the Service Backup VM via BOSH SSH or through the Ops Manager VM access method. Navigate to the Service Backup component logs, typically found in /var/vcap/sys/log/service-backup or similar log directories. Search log files for plaintext AWS access key ID strings (typically 20 characters starting with AKIA) or secret key patterns.
    Affected if Log files contain plaintext AWS_ACCESS_KEY_ID or AWS_SECRET_ACCESS_KEY values, or strings resembling AWS credentials

A user is affected if the MySQL for PCF tile version is 1.7.0 through 1.7.7, the Service Backup component is enabled, and Service Backup logs contain plaintext AWS credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade MySQL for PCF tiles to version 1.7.10 or later to resolve the plaintext credential logging. As a precaution, rotate any AWS access keys that may have been logged since the vulnerability could still be exploited if an attacker gains access to the Service Backup VM.

Recommended fix High confidence

MySQL for PCF tile version 1.7.10 or later

  1. Download MySQL for PCF tile version 1.7.10 or later from Pivotal Network
  2. Log in to Pivotal Ops Manager
  3. Navigate to the MySQL for PCF tile in the Installation Dashboard
  4. Select 'Upgrade' to apply the new tile version
  5. Apply changes using Ops Manager to complete the upgrade
  6. Verify that AWS credentials are no longer logged in plaintext in the Service Backup component logs

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pivotal Software Mysql Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-0898 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-0898 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data