# CVE-2018-10919: Information disclosure in samba

> An authenticated attacker can extract confidential attribute values from the Samba Active Directory LDAP server due to missing access control checks.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2018-10919, DEBIAN-CVE-2018-10919, ECHO-9966-da92-510a, GHSA-2h4c-mfg2-2f7f, SUSE-SU-2018:3161-1, UBUNTU-CVE-2018-10919

## What is CVE-2018-10919?

CVE-2018-10919 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 22 Aug 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Samba Active Directory LDAP server was vulnerable to an information disclosure flaw because of missing access control checks. An authenticated attacker could use this flaw to extract confidential attribute values using LDAP search expressions. Samba versions before 4.6.16, 4.7.9 and 4.8.4 are vulnerable.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), CWE-203 (Observable Discrepancy)

## Which versions are affected by CVE-2018-10919?

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `samba` | SUSE:Enterprise Storage 5 | All versions | 4.6.16+git.124.aee309c5c18-3.32.1 |
| `samba` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 4.6.16+git.124.aee309c5c18-3.32.1 |
| `samba` | SUSE:Linux Enterprise High Availability Extension 12 SP3 | All versions | 4.6.16+git.124.aee309c5c18-3.32.1 |
| `samba` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 4.6.16+git.124.aee309c5c18-3.32.1 |
| `samba` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 4.6.16+git.124.aee309c5c18-3.32.1 |
| `samba` | SUSE:Linux Enterprise Software Development Kit 12 SP3 | All versions | 4.6.16+git.124.aee309c5c18-3.32.1 |

Products: Canonical Ubuntu Linux, Debian Debian Linux, Samba Samba.

## How do I fix CVE-2018-10919?

Upgrade to a fixed version.

## Is CVE-2018-10919 being exploited?

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

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-10919 and fix it if it is affected.

What it is: CVE-2018-10919 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 22 Aug 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-10919 in the wild and no public exploit code.

Affected product: Canonical Ubuntu Linux. 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-2018-10919/ (Markdown: https://insights.sbomify.com/CVE-2018-10919/index.md)
```

## Sources

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

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