CVE-2002-1323: Medium severity safe.pm safe.pm vulnerability

Published Dec 11, 2002
·
Updated

Safe.pm 2.0.7 and earlier, when used in Perl 5.8.0 and earlier, may allow attackers to break out of safe compartments in (1) Safe::reval or (2) Safe::rdo using a redefined @ variable, which is not reset between successive calls.

Affected Software

48 affected components
Safe.pm Safe.pm=2.0_7
Sun Linux=5.0.7
SGI IRIX=6.5.6
SGI IRIX=6.5.17f
SGI IRIX=6.5.1
SGI IRIX=6.5.10
SGI IRIX=6.5.17
SGI IRIX=6.5.12
SGI IRIX=6.5.18f
SGI IRIX=6.5.19f
SGI IRIX=6.5.21f
SGI IRIX=6.5.9
SGI IRIX=6.5.21m
SGI IRIX=6.5.19
SGI IRIX=6.5.17m
SGI IRIX=6.5.20m
SGI IRIX=6.5.15
SGI IRIX=6.5.3
SGI IRIX=6.5.14
SGI IRIX=6.5.8
SGI IRIX=6.5.19m
SGI IRIX=6.5.20f
Safe.pm Safe.pm=2.0_6
SGI IRIX=6.5.5
SGI IRIX=6.5.4
SGI IRIX=6.5.11
SGI IRIX=6.5.2
SGI IRIX=6.5
SGI IRIX=6.5.7
SGI IRIX=6.5.18
SGI IRIX=6.5.18m
SGI IRIX=6.5.22
SGI IRIX=6.5.13
SGI IRIX=6.5.16
SCO UnixWare=7.1.3
redhat Enterprise Linux=2.1
redhat Enterprise Linux=2.1
redhat Enterprise Linux=2.1
redhat Linux Advanced Workstation=2.1
Sun SunOS=5.8
Sun Solaris=9.0
SCO Open UNIX=8.0
Sun Solaris=9.0
redhat Enterprise Linux=2.1
redhat Enterprise Linux=2.1
SCO UnixWare=7.1.2
Sun Solaris=8.0
redhat Enterprise Linux=2.1

Event History

Dec 11, 2002
CVE Published
05:00 AM
Sep 1, 2004
CVE Published
via MITRE·08:00 AM
Data Sourced
via MITRE·08:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2002-1323?

CVE-2002-1323 is considered a high severity vulnerability due to its potential to allow code execution outside of safe compartments.

2

How do I fix CVE-2002-1323?

To fix CVE-2002-1323, upgrade to Safe.pm version 2.0.8 or later which addresses this vulnerability.

3

What software is affected by CVE-2002-1323?

Software using Safe.pm version 2.0.7 and earlier, particularly those deployed on Perl 5.8.0 and earlier, are affected by CVE-2002-1323.

4

What is the impact of exploiting CVE-2002-1323?

Exploiting CVE-2002-1323 can lead to unauthorized access to the underlying system, allowing attackers to execute arbitrary code.

5

Is there a workaround for CVE-2002-1323?

A temporary workaround for CVE-2002-1323 is to avoid using Safe::reval or Safe::rdo until the Safe.pm package has been upgraded.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203