dbcve.org
LinuxOperating system · Gentoo

CVE-2004-0418

HIGH · 10.0 CVSS v2.0 Published 2004-08-06
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
serve_notify in CVS 1.12.x through 1.12.8, and 1.11.x through 1.11.16, does not properly handle empty data lines, which may allow remote attackers to perform an "out-of-bounds" write for a single byte to execute arbitrary code or modify critical program data.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LinuxOperating system
Affected:= 1.4
CvsApplication
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= 1.11.5= 1.11.6= 1.11.10= 1.11.11
OpenpkgApplication
Affected:all versions= 1.3= 2.0
PropackApplication
Affected:= 2.4= 3.0
OpenBSDOperating system
Affected:all versions= 3.4= 3.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch www.debian.org →
Recommended fix High confidence

CVS 1.11.17+ or CVS 1.12.9+ (latest stable 1.12.x or 1.11.x release)

  1. 1. Identify the currently installed CVS version using 'cvs --version' or 'rpm -q cvs'
  2. 2. For CVS 1.11.x branch: upgrade to CVS 1.11.17 or later
  3. 3. For CVS 1.12.x branch: upgrade to CVS 1.12.9 or later
  4. 4. Obtain the fixed packages from your Linux distribution's security updates or compile from source from cvshome.org (https://ftp.gnu.org/non-gnu/cvs/)
  5. 5. After upgrading, verify the new version is installed: 'cvs --version'
  6. 6. Restart any CVS server processes (if running as a daemon) to ensure the patched version is active
Caveat Generally low risk - point release upgrades in CVS typically contain only bug and security fixes; ensure any custom scripts are tested against the new version

Generated from the published advisory — verify against the referenced sources before acting.

We can apply and verify the patch for your build — typical engagement from $1,950. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2004-0418 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2004-0418 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data