dbcve.org
SambaApplication

CVE-2016-2119

HIGH · 7.5 CVSS v3.1 Published 2016-07-07
Fix available
A fix is available. Upgrade to 4.2.14 / 4.3.11 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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
libcli/smb/smbXcli_base.c in Samba 4.x before 4.2.14, 4.3.x before 4.3.11, and 4.4.x before 4.4.5 allows man-in-the-middle attackers to bypass a client-signing protection mechanism, and consequently spoof SMB2 and SMB3 servers, via the (1) SMB2_SESSION_FLAG_IS_GUEST or (2) SMB2_SESSION_FLAG_IS_NULL flag.

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

A man-in-the-middle vulnerability in Samba's SMB2/SMB3 client-signing verification allows attackers to spoof SMB servers by manipulating the SMB2_SESSION_FLAG_IS_GUEST or SMB2_SESSION_FLAG_IS_NULL session flags, bypassing the signing protection mechanism.

MitigationUpgrade Samba to version 4.2.14 or later for 4.x, 4.3.11 or later for 4.3.x, or 4.4.5 or later for 4.4.x series.

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:>= 4.0.0, < 4.2.14>= 4.3.0, < 4.3.11>= 4.4.0, < 4.4.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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

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. Check installed Samba version
    Run `smbd --version` or `rpm -q samba` (RHEL/CentOS) or `dpkg -l samba` (Debian/Ubuntu) to identify the installed Samba version
    Affected if The version returned falls within 4.0.0 to 4.2.13, 4.3.0 to 4.3.10, or 4.4.0 to 4.4.4
  2. Verify SMB client functionality is in use
    Check if the `smbclient` utility is installed or if the system has SMB mount configurations in `/etc/fstab` or uses `mount.cifs`
    Affected if SMB client tools or CIFS mount capabilities are present on the system
  3. Confirm SMB client configuration
    Inspect `/etc/samba/smb.conf` for any `[global]` or share configurations, or check for active SMB sessions using `smbstatus`
    Affected if The system is configured as an SMB client connecting to remote shares or is running smbclient

A system is affected if it runs Samba versions 4.0.0-4.2.13, 4.3.0-4.3.10, or 4.4.0-4.4.4 and functions as an SMB client connecting to potentially untrusted SMB servers.

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 4.2.14 / 4.3.11 / 4.4.5 or later
Fixed in 4.2.144.3.114.4.5
Interim mitigation

Upgrade Samba to version 4.2.14 or later for 4.x, 4.3.11 or later for 4.3.x, or 4.4.5 or later for 4.4.x series.

Fix this in Samba Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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