Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2002-1323: Safe.pm 2.0.7 and earlier, when used in Perl 5.8.0 and earlier, may allow attackers to break out of safe compa

31
Routine
MEDIUM 4.6WATCHLISTDOWNGRADEDOWNGRADEMITIGATE

CVE-2002-1323 is a medium-severity flaw (CVSS 4.6) affecting safe.pm, linux, irix. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • On your watchlist

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score4.6 (Medium)
EPSS exploit chance0.5% (top 60%)
CISA exploited listNo
Published2002-12-11
Last modified2026-06-16
Publisher (CNA): MITRE · Vendor: redhat · safe.pm · sco · sgi · sun

Share: LinkedIn · X · Reddit

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

safe.pm safe.pm DOWNGRADE
Affected: 2.0_6 · 2.0_7
Fixed in: no fixed release known
Safe to downgrade to: a release before 2.0_6
1. Check installed version
apt-cache policy safe.pm || rpm -q safe.pm || safe.pm --version
2. No fixed release: DOWNGRADE to a release before 2.0_6 (Debian / Ubuntu)
apt-cache madison safe.pm sudo apt install safe.pm=<VERSION_BEFORE_2.0_6> sudo apt-mark hold safe.pm
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list safe.pm sudo dnf downgrade safe.pm-<VERSION_BEFORE_2.0_6> sudo dnf versionlock add safe.pm
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
sun linux DOWNGRADE
Affected: 5.0.7
Fixed in: no fixed release known
Safe to downgrade to: a release before 5.0.7
1. Check installed version
apt-cache policy linux || rpm -q linux || linux --version
2. No fixed release: DOWNGRADE to a release before 5.0.7 (Debian / Ubuntu)
apt-cache madison linux sudo apt install linux=<VERSION_BEFORE_5.0.7> sudo apt-mark hold linux
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list linux sudo dnf downgrade linux-<VERSION_BEFORE_5.0.7> sudo dnf versionlock add linux
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
sgi irix MITIGATE
Affected: 6.5 · 6.5.1 · 6.5.2 · 6.5.3 · 6.5.4 · 6.5.5 · 6.5.6 · 6.5.7
Fixed in: no fixed release known
Safe to downgrade to: a release before 6.5
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
redhat enterprise linux MITIGATE
Affected: 2.1
Fixed in: no fixed release known
Safe to downgrade to: a release before 2.1
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
redhat linux advanced workstation MITIGATE
Affected: 2.1
Fixed in: no fixed release known
Safe to downgrade to: a release before 2.1
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
sco open unix MITIGATE
Affected: 8.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 8.0
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2002-1323?

safe.pm: downgrade or apply the listed mitigation; linux: downgrade or apply the listed mitigation; irix: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2002-1323 being exploited?

CVE-2002-1323 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2002-1323 affect?

CVE-2002-1323 affects safe.pm, linux, irix. Severity is medium (CVSS 4.6). 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.

How urgent is CVE-2002-1323?

Priority 31/100. On your watchlist

Software pages

Perl vulnerabilities

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.