First published: Thu Apr 04 2013(Updated: )
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."
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
PostgreSQL | =9.2 | |
PostgreSQL | =9.2.1 | |
PostgreSQL | =9.2.2 | |
PostgreSQL | =9.2.3 | |
PostgreSQL | =9.1 | |
PostgreSQL | =9.1.1 | |
PostgreSQL | =9.1.2 | |
PostgreSQL | =9.1.3 | |
PostgreSQL | =9.1.4 | |
PostgreSQL | =9.1.5 | |
PostgreSQL | =9.1.6 | |
PostgreSQL | =9.1.7 | |
PostgreSQL | =9.1.8 | |
PostgreSQL | =9.0 | |
PostgreSQL | =9.0.1 | |
PostgreSQL | =9.0.2 | |
PostgreSQL | =9.0.3 | |
PostgreSQL | =9.0.4 | |
PostgreSQL | =9.0.5 | |
PostgreSQL | =9.0.6 | |
PostgreSQL | =9.0.7 | |
PostgreSQL | =9.0.8 | |
PostgreSQL | =9.0.9 | |
PostgreSQL | =9.0.10 | |
PostgreSQL | =9.0.11 | |
PostgreSQL | =9.0.12 | |
PostgreSQL | =8.4 | |
PostgreSQL | =8.4.1 | |
PostgreSQL | =8.4.2 | |
PostgreSQL | =8.4.3 | |
PostgreSQL | =8.4.4 | |
PostgreSQL | =8.4.5 | |
PostgreSQL | =8.4.6 | |
PostgreSQL | =8.4.7 | |
PostgreSQL | =8.4.8 | |
PostgreSQL | =8.4.9 | |
PostgreSQL | =8.4.10 | |
PostgreSQL | =8.4.11 | |
PostgreSQL | =8.4.12 | |
PostgreSQL | =8.4.13 | |
PostgreSQL | =8.4.14 | |
PostgreSQL | =8.4.15 | |
PostgreSQL | =8.4.16 | |
Ubuntu | =8.04 | |
Ubuntu | =10.04 | |
Ubuntu | =11.10 | |
Ubuntu | =12.04 | |
Ubuntu | =12.10 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2013-1900 has a medium severity level due to its potential impact on cryptographic functions.
To fix CVE-2013-1900, upgrade PostgreSQL to version 9.2.4, 9.1.9, 9.0.13, or 8.4.17 or later.
CVE-2013-1900 affects PostgreSQL versions 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 that use OpenSSL.
The potential impacts of CVE-2013-1900 include insufficient randomness in cryptographic functions, which may compromise security.
There are no known effective workarounds for CVE-2013-1900 other than upgrading to a patched version of PostgreSQL.