high
8.5
CWE
264
Advisory Published
CVE Published
CVE Published
Updated

CVE-2010-1447

First published: Mon May 03 2010(Updated: )

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 <a href="https://access.redhat.com/security/cve/CVE-2010-1168">CVE-2010-1168</a>. Solution: Ugrade to Safe.pm v2.27 or higher. References: [1] <a href="http://search.cpan.org/~rgarcia/Safe-2.27/Safe.pm">http://search.cpan.org/~rgarcia/Safe-2.27/Safe.pm</a> 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.

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
redhat/perl<3:5.8.5-53.el4
3:5.8.5-53.el4
redhat/perl<4:5.8.8-32.el5_5.1
4:5.8.8-32.el5_5.1
PostgreSQL Common=7.4.16
PostgreSQL Common=7.4.24
PostgreSQL Common=7.4.22
PostgreSQL Common=7.4.21
PostgreSQL Common=7.4.19
PostgreSQL Common=7.4.15
PostgreSQL Common=7.4.1
PostgreSQL Common=7.4.14
PostgreSQL Common=7.4.26
PostgreSQL Common=7.4.6
PostgreSQL Common=7.4.23
PostgreSQL Common=7.4.11
PostgreSQL Common=7.4.7
PostgreSQL Common=7.4.17
PostgreSQL Common=7.4.3
PostgreSQL Common=7.4.25
PostgreSQL Common=7.4.9
PostgreSQL Common=7.4.5
PostgreSQL Common=7.4.18
PostgreSQL Common=7.4.8
PostgreSQL Common=7.4
PostgreSQL Common=7.4.4
PostgreSQL Common=7.4.28
PostgreSQL Common=7.4.12
PostgreSQL Common=7.4.27
PostgreSQL Common=7.4.10
PostgreSQL Common=7.4.20
PostgreSQL Common=7.4.2
PostgreSQL Common=7.4.13
PostgreSQL Common=8.0.7
PostgreSQL Common=8.0.2
PostgreSQL Common=8.0.22
PostgreSQL Common=8.0.17
PostgreSQL Common=8.0.10
PostgreSQL Common=8.0.12
PostgreSQL Common=8.0.9
PostgreSQL Common=8.0.15
PostgreSQL Common=8.0.0
PostgreSQL Common=8.0.18
PostgreSQL Common=8.0.3
PostgreSQL Common=8.0.24
PostgreSQL Common=8.0.20
PostgreSQL Common=8.0.8
PostgreSQL Common=8.0.6
PostgreSQL Common=8.0.16
PostgreSQL Common=8.0.13
PostgreSQL Common=8.0.1
PostgreSQL Common=8.0.19
PostgreSQL Common=8.0.21
PostgreSQL Common=8.0.23
PostgreSQL Common=8.0.4
PostgreSQL Common=8.0.5
PostgreSQL Common=8.0.14
PostgreSQL Common=8.0.11
PostgreSQL Common=8.0
PostgreSQL Common=8.1.10
PostgreSQL Common=8.1.6
PostgreSQL Common=8.1.15
PostgreSQL Common=8.1.7
PostgreSQL Common=8.1.20
PostgreSQL Common=8.1
PostgreSQL Common=8.1.19
PostgreSQL Common=8.1.13
PostgreSQL Common=8.1.0
PostgreSQL Common=8.1.3
PostgreSQL Common=8.1.9
PostgreSQL Common=8.1.14
PostgreSQL Common=8.1.11
PostgreSQL Common=8.1.17
PostgreSQL Common=8.1.18
PostgreSQL Common=8.1.4
PostgreSQL Common=8.1.8
PostgreSQL Common=8.1.1
PostgreSQL Common=8.1.12
PostgreSQL Common=8.1.5
PostgreSQL Common=8.1.16
PostgreSQL Common=8.1.2
PostgreSQL Common=8.2.9
PostgreSQL Common=8.2.10
PostgreSQL Common=8.2.15
PostgreSQL Common=8.2.4
PostgreSQL Common=8.2.11
PostgreSQL Common=8.2.12
PostgreSQL Common=8.2.2
PostgreSQL Common=8.2.5
PostgreSQL Common=8.2.1
PostgreSQL Common=8.2.7
PostgreSQL Common=8.2.6
PostgreSQL Common=8.2.3
PostgreSQL Common=8.2.16
PostgreSQL Common=8.2.8
PostgreSQL Common=8.2.13
PostgreSQL Common=8.2
PostgreSQL Common=8.2.14
PostgreSQL Common=8.3.6
PostgreSQL Common=8.3.3
PostgreSQL Common=8.3.2
PostgreSQL Common=8.3.1
PostgreSQL Common=8.3.5
PostgreSQL Common=8.3.8
PostgreSQL Common=8.3.7
PostgreSQL Common=8.3.10
PostgreSQL Common=8.3
PostgreSQL Common=8.3.4
PostgreSQL Common=8.3.9
PostgreSQL Common=8.4.1
PostgreSQL Common=8.4.3
PostgreSQL Common=8.4
PostgreSQL Common=8.4.2
PostgreSQL Common=9.0.0-beta1

Remedy

http://www.vupen.com/english/advisories/2010/1167

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Parent vulnerabilities

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

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203