CVE-2003-0606: sup 1.8 and earlier does not properly create temporary files, which allows local users to overwrite arbitrary

Routine

MEDIUM 4.6DOWNGRADEDOWNGRADE

CVE-2003-0606 is a medium-severity flaw (CVSS 4.6) affecting cvsup-mirror, sup. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

sup 1.8 and earlier does not properly create temporary files, which allows local users to overwrite arbitrary files.

Why this priority

No elevated risk signals yet

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

Risk facts

CVSS score	4.6 (Medium)
EPSS exploit chance	0.3% (top 75%)
CISA exploited list	No
Published	2003-08-27
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: cvsup · sup

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

Am I affected?

Timeline

2003-08-27 04:00 UTCPublished CVE record published
2026-06-16 22:02 UTCUpdated Record last modified

cvsup cvsup-mirror DOWNGRADE

Affected: 1.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.2

1. Check installed version

apt-cache policy cvsup-mirror || rpm -q cvsup-mirror || cvsup-mirror --version

2. No fixed release: DOWNGRADE to a release before 1.2 (Debian / Ubuntu)

apt-cache madison cvsup-mirror sudo apt install cvsup-mirror=<VERSION_BEFORE_1.2> sudo apt-mark hold cvsup-mirror

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list cvsup-mirror sudo dnf downgrade cvsup-mirror-<VERSION_BEFORE_1.2> sudo dnf versionlock add cvsup-mirror

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.

sup sup DOWNGRADE

Affected: 1.8

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.8

1. Check installed version

apt-cache policy sup || rpm -q sup || sup --version

2. No fixed release: DOWNGRADE to a release before 1.8 (Debian / Ubuntu)

apt-cache madison sup sudo apt install sup=<VERSION_BEFORE_1.8> sudo apt-mark hold sup

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list sup sudo dnf downgrade sup-<VERSION_BEFORE_1.8> sudo dnf versionlock add sup

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.

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-2003-0606?

cvsup-mirror: downgrade or apply the listed mitigation; sup: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2003-0606 being exploited?

CVE-2003-0606 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-2003-0606 affect?

CVE-2003-0606 affects cvsup-mirror, sup. Severity is medium (CVSS 4.6). sup 1.8 and earlier does not properly create temporary files, which allows local users to overwrite arbitrary files.

How urgent is CVE-2003-0606?

Priority 22/100. No elevated risk signals yet.

References

← Back to latest CVEs