dbcve.org
SambaApplication

CVE-2012-1182

HIGH · 10.0 CVSS v2.0 Published 2012-04-10
Fix available
A fix is available. Upgrade to after 3.4.15 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS 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
The RPC code generator in Samba 3.x before 3.4.16, 3.5.x before 3.5.14, and 3.6.x before 3.6.4 does not implement validation of an array length in a manner consistent with validation of array memory allocation, which allows remote attackers to execute arbitrary code via a crafted RPC call.

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

The RPC code generator in Samba versions 3.x before 3.4.16, 3.5.x before 3.5.14, and 3.6.x before 3.6.4 fails to validate array length consistently with array memory allocation, allowing remote attackers to execute arbitrary code via crafted RPC calls with specially crafted array parameters that overflow allocated buffers.

MitigationUpgrade to Samba 3.4.16, 3.5.14, 3.6.4 or later. If immediate patching is not feasible, restrict network access to RPC interfaces via firewall rules or disable unnecessary RPC services to reduce 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
SambaApplication
Affected:<= 3.4.15= 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= 3.0.8= 3.0.9

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

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 `smbd --version` or `samba --version`; on Linux you can also use `rpm -q samba` or `dpkg -l samba`
    Affected if The version number is lower than 3.4.16, 3.5.14, or 3.6.4 (for 3.x, 3.5.x, and 3.6.x branches respectively)
  2. Confirm Samba services are running
    Check if the `smbd` daemon is running using `ps aux | grep smbd` or `systemctl status smbd`
    Affected if The smbd process is active, as the vulnerability exists in the RPC code generator used by smbd
  3. Verify RPC listeners are exposed
    Check for open ports 139 and 445 using `netstat -tlnp | grep -E ':(139|445)'` or `ss -tlnp | grep -E ':(139|445)'`
    Affected if Ports 139 (NetBIOS) or 445 (SMB directly) are listening, as these allow RPC calls to reach the vulnerable code generator
  4. Check network accessibility of SMB/RPC services
    Review firewall rules (`iptables -L` or `firewall-cmd --list-all`) and network configuration to determine if these ports are reachable from untrusted networks
    Affected if The RPC ports are accessible from network segments that include untrusted or attacker-controlled systems

You are affected if your Samba version is below the fixed releases AND the RPC service (ports 139/445) is running and network-accessible.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 3.4.15
Interim mitigation

Upgrade to Samba 3.4.16, 3.5.14, 3.6.4 or later. If immediate patching is not feasible, restrict network access to RPC interfaces via firewall rules or disable unnecessary RPC services to reduce attack surface.

Recommended fix High confidence

Samba 3.4.16+ (or 3.5.14+ or 3.6.4+ depending on your branch)

  1. 1. Identify the current Samba version installed by running 'smbd --version' or 'samba --version'
  2. 2. Stop all Samba services (smbd, nmbd, winbindd) using 'service smbd stop' or equivalent for your system
  3. 3. Backup the Samba configuration file (smb.conf) typically located at /etc/samba/smb.conf
  4. 4. Upgrade Samba to version 3.4.16 or later, 3.5.14 or later, or 3.6.4 or later using your system's package manager (e.g., yum update samba, apt-get install samba, or zypper update samba)
  5. 5. Verify the new Samba version is installed: 'smbd --version'
  6. 6. Review and restore the Samba configuration file if needed
  7. 7. Start Samba services: 'service smbd start' or equivalent
  8. 8. Verify the service is running and responding: 'smbclient -L localhost'
Caveat Major version upgrades may introduce configuration changes; review smb.conf for deprecated options and test thoroughly before production deployment

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

Fix this in Samba Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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