Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2004-0416: Double free vulnerability for the error_prog_name string in CVS 1.12.x through 1.12.8, and 1.11.x through 1.11

69
This week
HIGH 10.0WATCHLISTDOWNGRADEDOWNGRADEDOWNGRADE

CVE-2004-0416 is a high-severity flaw (CVSS 10.0) affecting cvs, openpkg, propack. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Double free vulnerability for the error_prog_name string in CVS 1.12.x through 1.12.8, and 1.11.x through 1.11.16, may allow remote attackers to execute arbitrary code.

Why this priority

  • Critical severity
  • EPSS top 4%: very likely to be exploited
  • Public exploit reference
  • On your watchlist

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

Risk facts

CVSS score10.0 (High)
EPSS exploit chance13.2% (top 4%)
CISA exploited listNo
WeaknessCWE-119
Published2004-08-06
Last modified2026-06-16
Publisher (CNA): MITRE · Vendor: cvs · gentoo · openbsd · openpkg · sgi

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

cvs cvs DOWNGRADE
Affected: 1.10.7 · 1.10.8 · 1.11 · 1.11.1 · 1.11.1_p1 · 1.11.2 · 1.11.3 · 1.11.4
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.10.7
1. Check installed version
apt-cache policy cvs || rpm -q cvs || cvs --version
2. No fixed release: DOWNGRADE to a release before 1.10.7 (Debian / Ubuntu)
apt-cache madison cvs sudo apt install cvs=<VERSION_BEFORE_1.10.7> sudo apt-mark hold cvs
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list cvs sudo dnf downgrade cvs-<VERSION_BEFORE_1.10.7> sudo dnf versionlock add cvs
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.
openpkg openpkg DOWNGRADE
Affected: all versions · 1.3 · 2.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.3
1. Check installed version
apt-cache policy openpkg || rpm -q openpkg || openpkg --version
2. No fixed release: DOWNGRADE to a release before 1.3 (Debian / Ubuntu)
apt-cache madison openpkg sudo apt install openpkg=<VERSION_BEFORE_1.3> sudo apt-mark hold openpkg
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list openpkg sudo dnf downgrade openpkg-<VERSION_BEFORE_1.3> sudo dnf versionlock add openpkg
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 propack DOWNGRADE
Affected: 2.4 · 3.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 2.4
1. Check installed version
apt-cache policy propack || rpm -q propack || propack --version
2. No fixed release: DOWNGRADE to a release before 2.4 (Debian / Ubuntu)
apt-cache madison propack sudo apt install propack=<VERSION_BEFORE_2.4> sudo apt-mark hold propack
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list propack sudo dnf downgrade propack-<VERSION_BEFORE_2.4> sudo dnf versionlock add propack
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.
gentoo linux MITIGATE
Affected: 1.4
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.4
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.
openbsd openbsd MITIGATE
Affected: all versions · 3.4 · 3.5
Fixed in: no fixed release known
Safe to downgrade to: a release before 3.4
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.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

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-2004-0416?

cvs: downgrade or apply the listed mitigation; openpkg: downgrade or apply the listed mitigation; propack: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2004-0416 being exploited?

CVE-2004-0416 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-2004-0416 affect?

CVE-2004-0416 affects cvs, openpkg, propack. Severity is high (CVSS 10.0). Double free vulnerability for the error_prog_name string in CVS 1.12.x through 1.12.8, and 1.11.x through 1.11.16, may allow remote attackers to execute arbitrary code.

How urgent is CVE-2004-0416?

Priority 69/100. Critical severity; EPSS top 4%: very likely to be exploited; Public exploit reference; On your watchlist

Related CVEs

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.