# CVE-2018-1057: Missing authorization in Samba

> Authenticated users can modify any other user's password, including administrators, due to incorrect LDAP permission validation in Samba AD DC.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2018-1057, AZL-7346, DEBIAN-CVE-2018-1057, ECHO-1ee2-55c5-a468, GHSA-6r4h-vw53-wmvv, SUSE-SU-2018:1687-1, UBUNTU-CVE-2018-1057

## What is CVE-2018-1057?

CVE-2018-1057 is a high-severity missing authorization vulnerability in Canonical Ubuntu Linux, published on 13 Mar 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

On a Samba 4 AD DC the LDAP server in all versions of Samba from 4.0.0 onwards incorrectly validates permissions to modify passwords over LDAP allowing authenticated users to change any other users' passwords, including administrative users and privileged service accounts (eg Domain Controllers).

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 3 products.


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

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

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

Apply the vendor's patch.

## Is CVE-2018-1057 being exploited?

There is no known exploitation of CVE-2018-1057 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-1057 and fix it if it is affected.

What it is: CVE-2018-1057 is a high-severity missing authorization vulnerability in Canonical Ubuntu Linux, published on 13 Mar 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-1057 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-1057/ (Markdown: https://insights.sbomify.com/CVE-2018-1057/index.md)
```

## Sources

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

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