LiveActive security incident?Get immediate response
CVE Record

CVE-2020-25694: A flaw was found in PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20...

A flaw was found in PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24. If a client application that creates additional database connections only reuses the basic connection parameters while dropping security-relevant parameters, an opportunity for a man-in-the-middle attack, or the ability to observe clear-text transmissions, could exist. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Older PostgreSQL releases can become unsafe when an application opens extra database connections but carries forward only basic settings and drops security-related connection parameters. In that situation, traffic that was expected to be protected could be exposed to interception or manipulation.

Executive priority

Treat this as a targeted confidentiality and integrity risk rather than a broad unauthenticated server takeover. Prioritize remediation where old PostgreSQL versions are used by applications that manage multiple connections or where database traffic may traverse untrusted networks.

Technical view

CVE-2020-25694 affects PostgreSQL versions before 13.1, 12.5, 11.10, 10.15, 9.6.20, and 9.5.24. The flaw is tied to client applications that create additional connections while omitting security-relevant parameters, creating possible man-in-the-middle or clear-text observation exposure.

Likely exposure

Exposure is most likely in environments running affected PostgreSQL versions with applications that programmatically create secondary database connections. Risk is higher where database traffic crosses untrusted or shared networks and where connection security parameters are not consistently preserved.

Exploitation context

The provided sources do not identify active exploitation, and the CVE is not marked KEV. Abuse appears conditional: an attacker needs the opportunity to observe or interfere with database traffic and an application behavior that drops security-relevant connection parameters.

Researcher notes

Evidence is limited to public advisory descriptions. The key validation point is application behavior, not just server version: determine whether connection parameters are dropped when additional PostgreSQL connections are created. No exploit status or CVSS score is provided in the source bundle.

Mitigation direction

  • Upgrade PostgreSQL to the fixed versions or a later supported release.
  • Review PostgreSQL, OS distribution, and appliance vendor advisories for package-specific guidance.
  • Audit applications that create additional database connections for parameter preservation.
  • Avoid database traffic over untrusted networks unless connection security settings are enforced.

Validation and detection

  • Inventory PostgreSQL versions and identify instances older than the fixed releases.
  • Review connection-handling code for secondary or recreated database connections.
  • Confirm security-relevant connection parameters are retained across all connection paths.
  • Check Debian, Gentoo, NetApp, and PostgreSQL advisories against deployed packages.
Prepared
Confidence
medium
Sources
6

Public sources used

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

CWE-327: 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 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-25694 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
6Source 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
n/apostgresqlAll PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24Listed
Weakness

CWE details

CWE-327

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

CWE-327 · source CWE mapping

Use of a Broken or Risky Cryptographic Algorithm

Use of a Broken or Risky Cryptographic Algorithm represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs