Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2004-2012: The systrace_exit function in the systrace utility for NetBSD-current and 2.0 before April 16, 2004, and certa

45
This month
HIGH 7.2DOWNGRADEDOWNGRADEMITIGATE

CVE-2004-2012 is a high-severity flaw (CVSS 7.2) affecting provos systrace, systrace port for freebsd, netbsd. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The systrace_exit function in the systrace utility for NetBSD-current and 2.0 before April 16, 2004, and certain FreeBSD ports, does not verify the owner of the /dec/systrace connection before setting euid to 0, which allows local users to gain root privileges.

Why this priority

  • High severity
  • Public exploit reference

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

Risk facts

CVSS score7.2 (High)
EPSS exploit chance0.9% (top 42%)
CISA exploited listNo
Published2004-12-31
Last modified2026-06-16
Publisher (CNA): MITRE · Vendor: netbsd · niels · vladimir kotal

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

niels provos systrace DOWNGRADE
Affected: 1.1 · 1.2 · 1.3 · 1.4 · 1.5
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.1
1. Check installed version
apt-cache policy provos-systrace || rpm -q provos-systrace || provos-systrace --version
2. No fixed release: DOWNGRADE to a release before 1.1 (Debian / Ubuntu)
apt-cache madison provos-systrace sudo apt install provos-systrace=<VERSION_BEFORE_1.1> sudo apt-mark hold provos-systrace
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list provos-systrace sudo dnf downgrade provos-systrace-<VERSION_BEFORE_1.1> sudo dnf versionlock add provos-systrace
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.
vladimir kotal systrace port for freebsd DOWNGRADE
Affected: 2004-03-09 · 2004-06-02
Fixed in: no fixed release known
Safe to downgrade to: a release before 2004-03-09
1. Check installed version
apt-cache policy systrace-port-for-freebsd || rpm -q systrace-port-for-freebsd || systrace-port-for-freebsd --version
2. No fixed release: DOWNGRADE to a release before 2004-03-09 (Debian / Ubuntu)
apt-cache madison systrace-port-for-freebsd sudo apt install systrace-port-for-freebsd=<VERSION_BEFORE_2004-03-09> sudo apt-mark hold systrace-port-for-freebsd
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list systrace-port-for-freebsd sudo dnf downgrade systrace-port-for-freebsd-<VERSION_BEFORE_2004-03-09> sudo dnf versionlock add systrace-port-for-freebsd
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.
netbsd netbsd MITIGATE
Affected: 2.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 2.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.

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-2012?

provos systrace: downgrade or apply the listed mitigation; systrace port for freebsd: downgrade or apply the listed mitigation; netbsd: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2004-2012 being exploited?

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

CVE-2004-2012 affects provos systrace, systrace port for freebsd, netbsd. Severity is high (CVSS 7.2). The systrace_exit function in the systrace utility for NetBSD-current and 2.0 before April 16, 2004, and certain FreeBSD ports, does not verify the owner of the /dec/systrace connection before setting euid to 0, which allows local users to

How urgent is CVE-2004-2012?

Priority 45/100. High severity; Public exploit reference

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.