dbcve.org
Ubuntu LinuxOperating system · Canonical

CVE-2018-1057

HIGH · 8.8 CVSS v3.1 Published 2018-03-13
Fix available
A fix is available. Upgrade to 4.5.16 / 4.6.14 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
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).

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 LDAP server in Samba 4 AD DC versions 4.0.0 and later incorrectly validates permissions for password modifications over LDAP, allowing any authenticated user to change passwords for any other user including administrative accounts and privileged service accounts.

MitigationUpgrade to a patched Samba version that addresses the permission validation flaw in the LDAP password modification functionality.

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
Ubuntu LinuxOperating system
Affected:= 14.04= 16.04= 17.10
Debian LinuxOperating system
Affected:= 8.0
SambaApplication
Affected:>= 4.0.0, < 4.5.16>= 4.6.0, < 4.6.14>= 4.7.0, < 4.7.6

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
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Identify Samba installation and version
    Run 'samba --version' or check package manager: 'dpkg -l | grep samba' on Debian/Ubuntu, or 'rpm -qa | grep samba' on RHEL-based systems
    Affected if Version is >= 4.0.0 and < 4.5.16, OR >= 4.6.0 and < 4.6.14, OR >= 4.7.0 and < 4.7.6
  2. Confirm Samba is running as Active Directory Domain Controller
    Check smb.conf for 'server role = active directory domain controller' or run 'samba-tool domain info 127.0.0.1' to query AD DC status
    Affected if Samba is configured as AD DC (the vulnerability only affects AD DC implementations)
  3. Verify LDAP server is enabled and accessible
    Check smb.conf for 'ldap server require strong auth = no' or test LDAP connectivity with 'ldapsearch -h localhost -p 389 -D "CN=Administrator,CN=Users,DC=domain,DC=local" -W'
    Affected if LDAP server is enabled and accepts connections (the flaw is in LDAP password modification)
  4. Check LDAP password modification permissions
    Review AD DC access controls: run 'samba-tool ldapcmp' to compare DC configurations, or examine 'dsdb' ACLs for password modify permissions on user objects
    Affected if Any authenticated LDAP user can modify passwords for privileged accounts (unrestricted password modification)
  5. Compare installed version to vulnerable ranges
    If version is 4.0.0 through 4.5.15, 4.6.0 through 4.6.13, or 4.7.0 through 4.7.5, the installation is in a vulnerable version range
    Affected if Samba version falls within any of the vulnerable version ranges AND runs as AD DC with LDAP enabled

If Samba 4.0.0+ is running as an AD DC with LDAP enabled and the version is within the vulnerable ranges (pre-4.5.16, pre-4.6.14, or pre-4.7.6), then the environment is affected by this CVE.

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.5.16 / 4.6.14 / 4.7.6 or later
Fixed in 4.5.164.6.144.7.6
Interim mitigation

Upgrade to a patched Samba version that addresses the permission validation flaw in the LDAP password modification functionality.

Fix this in Ubuntu Linux Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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