dbcve.org
Ubuntu LinuxOperating system · Canonical

CVE-2010-3069

HIGH · 7.5 CVSS v2.0 Published 2010-09-15
Fix available
A fix is available. Upgrade to 3.4.9 / 3.5.5 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Stack-based buffer overflow in the (1) sid_parse and (2) dom_sid_parse functions in Samba before 3.5.5 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted Windows Security ID (SID) on a file share.

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 · high confidence

Stack-based buffer overflow in Samba's sid_parse and dom_sid_parse functions allows remote attackers to cause denial of service and potentially execute arbitrary code via a crafted Windows Security ID (SID) sent to a file share. The vulnerability exists in versions of Samba prior to 3.5.5.

MitigationUpgrade Samba to version 3.5.5 or later to patch the vulnerable SID parsing functions. If immediate patching is not possible, restrict unauthenticated access to file shares to limit attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Ubuntu LinuxOperating system
Affected:= 6.06= 8.04= 9.04= 9.10= 10.04
SambaApplication
Affected:>= 3.0.0, <= 3.3.14>= 3.4.0, < 3.4.9>= 3.5.0, < 3.5.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
Partial
Integrity
Partial
Availability
Partial

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Samba version
    Run 'smbstatus --version' or 'rpm -q samba' or 'dpkg -l samba' depending on your Linux distribution
    Affected if The version is between 3.0.0 and 3.3.14 inclusive, between 3.4.0 and 3.4.8 inclusive, or between 3.5.0 and 3.5.4 inclusive
  2. Verify Samba daemon is running
    Run 'ps aux | grep smbd' or check service status with 'systemctl status smbd' or 'service smbd status'
    Affected if The smbd process is active and accepting connections
  3. Confirm file sharing is enabled
    Check for active shares using 'smbstatus -L' or 'net share' on Windows, or review /etc/samba/smb.conf for valid share definitions
    Affected if Any file share is exported and accessible to users or guests
  4. Determine if Samba is configured as a domain member
    Review /etc/samba/smb.conf for 'security = domain' or 'security = ads' settings, or check for 'winbind' in active processes with 'ps aux | grep winbind'
    Affected if The system is joined to a Windows domain or Active Directory domain, which triggers SID parsing when communicating with domain controllers

If the Samba version falls within any of the affected ranges AND the Samba server is running with accessible file shares, the environment is potentially vulnerable to CVE-2010-3069.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Upgrade available Upgrade to 3.4.9 / 3.5.5 or later
Fixed in 3.4.93.5.5
Interim mitigation

Upgrade Samba to version 3.5.5 or later to patch the vulnerable SID parsing functions. If immediate patching is not possible, restrict unauthenticated access to file shares to limit attack surface.

Fix this in Ubuntu Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-3069 — 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-2010-3069 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