dbcve.org
LinuxOperating system · Conectiva

CVE-2004-0882

HIGH · 10.0 CVSS v2.0 Published 2005-01-27
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
Buffer overflow in the QFILEPATHINFO request handler in Samba 3.0.x through 3.0.7 may allow remote attackers to execute arbitrary code via a TRANSACT2_QFILEPATHINFO request with a small "maximum data bytes" value.

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:= 10.0
Enterprise LinuxOperating system
Affected:= 2.1= 3.0
Enterprise Linux DesktopOperating system
Affected:= 3.0
Fedora CoreOperating system
Affected:= core_2.0= core_3.0
Linux Advanced WorkstationOperating system
Affected:= 2.1
Ubuntu LinuxOperating system
Affected:= 4.1
SambaApplication
Affected:= 3.0.0= 3.0.1= 3.0.2= 3.0.2a= 3.0.3= 3.0.4= 3.0.5= 3.0.6= 3.0.7

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.trustix.net →
Recommended fix High confidence

Samba 3.0.8 or later (preferably latest stable 3.0.x release)

  1. 1. Identify the current Samba version installed: smbd --version or rpm -q samba
  2. 2. Stop the Samba services: service smb stop or /etc/init.d/smb stop
  3. 3. Update the package repository to access fixed Samba packages
  4. 4. Install the fixed Samba package (upgrade to 3.0.8 or later): yum update samba or apt-get install samba (for Debian/Ubuntu)
  5. 5. Verify the new version is installed: smbd --version
  6. 6. Restart Samba services: service smb start or /etc/init.d/smb start
  7. 7. Review smb.conf for any custom configurations that may need adjustment after upgrade
Caveat Samba upgrade may require configuration review; ensure smb.conf is compatible with the new version before production deployment

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-0882 — 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-0882 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