LiveActive security incident?Get immediate response
CVE Record

CVE-2020-5406: PCF Autoscaling logs its database credentials

VMware Tanzu Application Service for VMs, 2.6.x versions prior to 2.6.18, 2.7.x versions prior to 2.7.11, and 2.8.x versions prior to 2.8.5, includes a version of PCF Autoscaling that writes database connection properties to its log, including database username and password. A malicious user with access to those logs may gain unauthorized access to the database being used by Autoscaling.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

PCF Autoscaling in affected VMware Tanzu Application Service for VMs releases logged database connection details, including username and password. Anyone who could read those logs could potentially use the credentials to access the Autoscaling database without authorization.

Executive priority

Treat this as a focused credential-exposure issue. Prioritize remediation if affected TAS versions were used and operational logs are broadly accessible or retained in shared logging systems.

Technical view

CVE-2020-5406 is a CWE-522 credential exposure issue in PCF Autoscaling bundled with TAS for VMs 2.6.x before 2.6.18, 2.7.x before 2.7.11, and 2.8.x before 2.8.5. Database connection properties, including credentials, were written to logs.

Likely exposure

Exposure is likely limited to organizations running the affected TAS for VMs versions where PCF Autoscaling logs are retained or accessible to users, operators, support tools, or centralized logging systems.

Exploitation context

The provided sources do not show active exploitation or CISA KEV listing. Abuse requires access to affected logs, but those logs may contain usable database credentials if generated before remediation.

Researcher notes

The source bundle names one affected product family and fixed version thresholds. No CVSS score, exploit details, or broader impact data is provided, so assessment should stay scoped to Autoscaling database credential exposure through logs.

Mitigation direction

  • Upgrade TAS for VMs to 2.6.18, 2.7.11, 2.8.5, or later supported releases.
  • Review VMware Tanzu guidance for any environment-specific remediation steps.
  • Rotate Autoscaling database credentials if affected logs may have been exposed.
  • Restrict access to historical and centralized logs containing Autoscaling output.
  • Remove or protect retained logs that contain database connection properties.

Validation and detection

  • Inventory TAS for VMs versions and identify affected 2.6.x, 2.7.x, or 2.8.x deployments.
  • Confirm whether PCF Autoscaling was enabled in affected deployments.
  • Review Autoscaling logs for database connection properties or exposed credentials.
  • Check centralized logging platforms for retained copies of affected log entries.
  • Verify Autoscaling database credentials were rotated after remediation.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

CWE-522: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. 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 lookup
description · low confidence lookup

Credential 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 lookup
description · low confidence lookup

Database 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 lookup
cve · low confidence lookup

CVE-2020-5406 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
PivotalVMware Tanzu Application Service for VMs2.8.x, 2.7.x, 2.6.xListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-522 · source CWE mapping

Insufficiently Protected Credentials

Insufficiently Protected Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.