SambaApplication

CVE-2002-1318

HIGH · 10.0 CVSS v2.0 Published 2002-12-11
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
High EPSS 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 samba 2.2.2 through 2.2.6 allows remote attackers to cause a denial of service and possibly execute arbitrary code via an encrypted password that causes the overflow during decryption in which a DOS codepage string is converted to a little-endian UCS2 unicode string.

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
SambaApplication
Affected:= 2.2.2= 2.2.3= 2.2.4= 2.2.5= 2.2.6
IrixOperating system
Affected:= 6.5= 6.5.1= 6.5.2= 6.5.3= 6.5.4= 6.5.5= 6.5.6= 6.5.7= 6.5.8= 6.5.9= 6.5.10= 6.5.11
Cifs 9000 ServerApplication
Affected:= a.01.08= a.01.08.01= a.01.09

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

Samba 2.2.7 or later (or current stable 3.x/4.x branch)

  1. Identify the current Samba version by running: smbd --version or rpm -q samba
  2. Stop the Samba services: smbd, nmbd, and winbindd
  3. For Debian/Ubuntu: apt-get update && apt-get install samba
  4. For Red Hat/Fedora: yum update samba
  5. For source compilation: Download Samba 2.2.7 or later from https://www.samba.org/samba/download/
  6. Configure with: ./configure --prefix=/usr/local/samba
  7. Compile and install: make && make install
  8. Restart Samba services
Caveat Upgrading from Samba 2.2.x to 3.x/4.x may require configuration file changes (smb.conf) and different authentication settings; test thoroughly in non-production environment first

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-2002-1318 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2002-1318 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