CVE-2013-1900Not scoredCWE-189

CVE-2013-1900: Postgresql vulnerability

Postgresql

Vendor fix available · Affected: Postgresql · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

4.5%probability of exploitation in the next 30 days

91st percentile

050100

Higher than 91% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

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."

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Numeric Errors · Other weaknesses
Vendor: Postgresql
Published: April 2013
Band: Possible (1 to 10%), April 2013

CoverageNo articles yet

No CyberSIXT article names CVE-2013-1900 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References

9 more references are in the CVE record.