Unscored severity · published May 2, 2005
CVE-2005-0227
PostgreSQL (pgsql) 7.4.x, 7.2.x, and other versions allows local users to load arbitrary shared libraries and execute code via the LOAD extension
–
CVSS
0.5%
EPSS
No
On KEV
Description
PostgreSQL (pgsql) 7.4.x, 7.2.x, and other versions allows local users to load arbitrary shared libraries and execute code via the LOAD extension.
Exploitation
Is it being used?
Exploit prediction (EPSS)0.5% · higher than 43% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
PO
PostgreSQL · PostgreSQL
7.3.0 before 7.3.9; 7.4 before 7.4.7; 8.0 before 8.0.1 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2005-0227
CVE.org
https://www.cve.org/CVERecord?id=CVE-2005-0227
Patch
http://archives.postgresql.org/pgsql-announce/2005-02/msg00000.php
Vendor Advisory
http://archives.postgresql.org/pgsql-bugs/2005-01/msg00269.php
Mailing List
http://marc.info/?l=bugtraq&m=110726899107148&w=2
Third Party Advisory
http://secunia.com/advisories/12948
Third Party Advisory
http://security.gentoo.org/glsa/glsa-200502-08.xml
Third Party Advisory
http://www.debian.org/security/2005/dsa-668
More from PostgreSQL
9.8
CVE-2024-24213
Supabase PostgreSQL v15.1 was discovered to contain a SQL injection vulnerability via the component /pg_meta/default/query
9.8
CVE-2015-0244
PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1 does not properly handle errors while reading a protocol message,…
9.8
CVE-2015-3166
The snprintf implementation in PostgreSQL before 9.0.20, 9.1.x before 9.1.16, 9.2.x before 9.2.11, 9.3.x before 9.3.7, and 9.4.x before 9.4.2 does not properly handle system-call…
9.8
CVE-2019-10211
Postgresql Windows installer before versions 11.5, 10.10, 9.6.15, 9.5.19, 9.4.24 is vulnerable via bundled OpenSSL executing code from unprotected directory
9.8
CVE-2018-16850
postgresql before versions 11.1, 10.6 is vulnerable to a to SQL injection in pg_upgrade and pg_dump via CREATE TRIGGER
