CVE-2010-1447: High severity PostgreSQL postgresql vulnerability
Safe.pm 2.26 and earlier (except 2.20 through 2.23 if using a threads-enabled Perl), when used in Perl 5.10.0 and earlier, may allow attackers to break out of safe compartment in (1) Safe::reval or (2) Safe::rdo using subroutine references, whose execution is delayed to happen outside of the safe compartment. If a victim was tricked into running a specially-crafted Perl script, using Safe extension module, it could lead to intended Safe module restrictions bypass, if the returned subroutine reference was called from outside of the compartment. Different vulnerability than CVE-2010-1168.
Solution: Ugrade to Safe.pm v2.27 or higher.
References: [1] http://search.cpan.org/~rgarcia/Safe-2.27/Safe.pm
Acknowledgements:
Red Hat would like to thank Tim Bunce for responsibly reporting this flaw. Upstream credits also Rafaël Garcia-Suarez for discovering of this issue.
Other sources
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.
— Red Hat
Affected Software
Remediation
Patch Available
Event History
Parent advisories
This vulnerability appears in the following advisories.
Frequently Asked Questions
What is the severity of CVE-2010-1447?
CVE-2010-1447 is considered to have moderate severity due to its potential to allow attackers to escape safe compartments.
How do I fix CVE-2010-1447?
To fix CVE-2010-1447, upgrade to Safe.pm version 2.27 or later to prevent the exploitation of this vulnerability.
What software versions are affected by CVE-2010-1447?
CVE-2010-1447 affects Safe.pm versions 2.26 and earlier, specifically when used with Perl 5.10.0 and earlier.
Can CVE-2010-1447 be exploited remotely?
Yes, CVE-2010-1447 can potentially be exploited remotely if the affected software is accessible.
What steps should I take after discovering CVE-2010-1447 in my environment?
After discovering CVE-2010-1447, immediately apply the recommended software upgrade and monitor for any unusual activity.