LiveActive security incident?Get immediate response
CVE Record

CVE-2013-1900: PostgreSQL 9.2.x before 9.2.4, 9.1.x before 9.1.9, 9.0.x before 9.0.13, and 8.4.x before 8.4.17, when using...

PostgreSQL 9.2.x before 9.2.4, 9.1.x before 9.1.9, 9.0.x before 9.0.13, and 8.4.x before 8.4.17, when using OpenSSL, generates insufficiently random numbers, which might allow remote authenticated users to have an unspecified impact via vectors related to the "contrib/pgcrypto functions."

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This issue affects older PostgreSQL releases when built with OpenSSL and using pgcrypto. The database may produce weak random values, which can undermine security features that depend on randomness. The public record says impact is unspecified and requires a remote authenticated user. Exposure is most likely in legacy PostgreSQL deployments still running the affected release lines, especially where pgcrypto is installed or application logic depends on pgcrypto-generated random values. Current supported PostgreSQL branches are not identified as affected in the provided sources. Handle as a legacy exposure cleanup item unless critical business processes rely on affected pgcrypto randomness. The main urgency is removing obsolete PostgreSQL versions and confirming no security-sensitive workflow depends on weak generated randomness. Mitigation focus: Upgrade PostgreSQL to 9.2.4, 9.1.9, 9.0.13, 8.4.17, or later supported releases.; Use operating-system vendor advisories for packaged PostgreSQL builds.; Prioritize systems using pgcrypto for security-sensitive application behavior..

Prepared

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.

cve · low confidence lookup

CVE-2013-1900 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
1Source 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/an/an/aListed
Weakness

CWE details

No CWE listed

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