Vulnerabilities · 2010 · Postgresql
CVE-2010-1447
Postgresql vulnerability
The Safe (aka Safe.pm) module 2.26, and certain earlier versions, for Perl, as used in PostgreSQL 7.4 before 7.4.29, 8.0 before 8.0.25, 8.1 before 8.1.21, 8.2 before 8.2.17, 8.3 before 8.3.11, 8.4 before 8.4.4, and 9.0 Beta before 9.0 Beta 2, allows context-dependent attackers to bypass intended (1) Safe::reval and (2) Safe::rdo access restrictions, and inject and execute arbitrary code, via vectors involving subroutine references and delayed execution.
Affected products
Postgresql. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Postgresql runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- secunia.com/advisories/39845 · Vendor Advisory
- www.vupen.com/english/advisories/2010/1167 · Patch
- kb.juniper.net/InfoCenter/index?page=content&id=JSA10705
- osvdb.org/64756
- secunia.com/advisories/40049
- secunia.com/advisories/40052
- security-tracker.debian.org/tracker/CVE-2010-1447
- www.debian.org/security/2011/dsa-2267
- nvd.nist.gov/vuln/detail/CVE-2010-1447
- cve.org/CVERecord?id=CVE-2010-1447
More vulnerabilities in Postgresql products
CVE-2025-49146CVE-2024-10979CVE-2024-10978CVE-2024-10977CVE-2024-10976CVE-2024-7348CVE-2024-4317CVE-2024-1597All 168
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.