# CVE-2016-2119: Security feature bypass in n/a

> Man-in-the-middle attackers can bypass SMB client signing to spoof servers, affecting Samba deployments.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 7 Jul 2016
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-2119, ECHO-50ea-9c50-68b5, GHSA-6hfw-45v2-4p3j, RHSA-2016:1486, RHSA-2016:1487, RHSA-2016:1494, SUSE-SU-2016:2306-1, SUSE-SU-2016:2570-1, UBUNTU-CVE-2016-2119, USN-3092-1

## What is CVE-2016-2119?

CVE-2016-2119 is a high-severity vulnerability in Samba Samba, published on 7 Jul 2016. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2016-2119?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `samba4` | Red Hat:enterprise_linux:6::client | All versions | 0:4.2.10-7.el6_8 |
| `samba4-client` | Red Hat:enterprise_linux:6::client | All versions | 0:4.2.10-7.el6_8 |
| `samba4-common` | Red Hat:enterprise_linux:6::client | All versions | 0:4.2.10-7.el6_8 |
| `samba4-dc` | Red Hat:enterprise_linux:6::client | All versions | 0:4.2.10-7.el6_8 |
| `samba4-dc-libs` | Red Hat:enterprise_linux:6::client | All versions | 0:4.2.10-7.el6_8 |
| `samba4-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:4.2.10-7.el6_8 |
| `samba4-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:4.2.10-7.el6_8 |
| `samba4-libs` | Red Hat:enterprise_linux:6::client | All versions | 0:4.2.10-7.el6_8 |
| `samba4-pidl` | Red Hat:enterprise_linux:6::client | All versions | 0:4.2.10-7.el6_8 |
| `samba4-python` | Red Hat:enterprise_linux:6::client | All versions | 0:4.2.10-7.el6_8 |
| `samba4-test` | Red Hat:enterprise_linux:6::client | All versions | 0:4.2.10-7.el6_8 |
| `samba4-winbind` | Red Hat:enterprise_linux:6::client | All versions | 0:4.2.10-7.el6_8 |
| `samba4-winbind-clients` | Red Hat:enterprise_linux:6::client | All versions | 0:4.2.10-7.el6_8 |
| `samba4-winbind-krb5-locator` | Red Hat:enterprise_linux:6::client | All versions | 0:4.2.10-7.el6_8 |
| `samba4` | Red Hat:enterprise_linux:6::computenode | All versions | 0:4.2.10-7.el6_8 |
| `samba4-client` | Red Hat:enterprise_linux:6::computenode | All versions | 0:4.2.10-7.el6_8 |
| `samba4-common` | Red Hat:enterprise_linux:6::computenode | All versions | 0:4.2.10-7.el6_8 |
| `samba4-dc` | Red Hat:enterprise_linux:6::computenode | All versions | 0:4.2.10-7.el6_8 |
| `samba4-dc-libs` | Red Hat:enterprise_linux:6::computenode | All versions | 0:4.2.10-7.el6_8 |
| `samba4-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:4.2.10-7.el6_8 |
| `samba4-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:4.2.10-7.el6_8 |
| `samba4-libs` | Red Hat:enterprise_linux:6::computenode | All versions | 0:4.2.10-7.el6_8 |
| `samba4-pidl` | Red Hat:enterprise_linux:6::computenode | All versions | 0:4.2.10-7.el6_8 |
| `samba4-python` | Red Hat:enterprise_linux:6::computenode | All versions | 0:4.2.10-7.el6_8 |
| `samba4-test` | Red Hat:enterprise_linux:6::computenode | All versions | 0:4.2.10-7.el6_8 |
| `samba4-winbind` | Red Hat:enterprise_linux:6::computenode | All versions | 0:4.2.10-7.el6_8 |
| `samba4-winbind-clients` | Red Hat:enterprise_linux:6::computenode | All versions | 0:4.2.10-7.el6_8 |
| `samba4-winbind-krb5-locator` | Red Hat:enterprise_linux:6::computenode | All versions | 0:4.2.10-7.el6_8 |
| `samba4` | Red Hat:enterprise_linux:6::server | All versions | 0:4.2.10-7.el6_8 |
| `samba4-client` | Red Hat:enterprise_linux:6::server | All versions | 0:4.2.10-7.el6_8 |
| `samba4-common` | Red Hat:enterprise_linux:6::server | All versions | 0:4.2.10-7.el6_8 |
| `samba4-dc` | Red Hat:enterprise_linux:6::server | All versions | 0:4.2.10-7.el6_8 |
| `samba4-dc-libs` | Red Hat:enterprise_linux:6::server | All versions | 0:4.2.10-7.el6_8 |
| `samba4-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:4.2.10-7.el6_8 |
| `samba4-devel` | Red Hat:enterprise_linux:6::server | All versions | 0:4.2.10-7.el6_8 |
| `samba4-libs` | Red Hat:enterprise_linux:6::server | All versions | 0:4.2.10-7.el6_8 |
| `samba4-pidl` | Red Hat:enterprise_linux:6::server | All versions | 0:4.2.10-7.el6_8 |
| `samba4-python` | Red Hat:enterprise_linux:6::server | All versions | 0:4.2.10-7.el6_8 |
| `samba4-test` | Red Hat:enterprise_linux:6::server | All versions | 0:4.2.10-7.el6_8 |
| `samba4-winbind` | Red Hat:enterprise_linux:6::server | All versions | 0:4.2.10-7.el6_8 |

Products: Samba Samba.

## How do I fix CVE-2016-2119?

Upgrade to a fixed version.

## Is CVE-2016-2119 being exploited?

There is no known exploitation of CVE-2016-2119 in the wild and no public exploit code.

## Other vulnerabilities in Samba Samba

- [CVE-2012-1182](https://insights.sbomify.com/CVE-2012-1182/): Integer overflow in n/a (critical 10.0)
- [CVE-2007-2446](https://insights.sbomify.com/CVE-2007-2446/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0600](https://insights.sbomify.com/CVE-2004-0600/): Memory corruption in n/a (critical 10.0)
- [CVE-1999-0810](https://insights.sbomify.com/CVE-1999-0810/): Denial of service in n/a (critical 10.0)
- [CVE-1999-0182](https://insights.sbomify.com/CVE-1999-0182/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-2119 and fix it if it is affected.

What it is: CVE-2016-2119 is a high-severity vulnerability in Samba Samba, published on 7 Jul 2016. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-2119 in the wild and no public exploit code.

Affected product: Samba Samba. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-2119/ (Markdown: https://insights.sbomify.com/CVE-2016-2119/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-2119
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-2119
- OSV: https://osv.dev/vulnerability/CVE-2016-2119

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-2119/
Summaries are generated and may contain mistakes; the official description above is the record.
