dbcve.org
Ubuntu LinuxOperating system · Canonical

CVE-2020-10760

MEDIUM · 6.5 CVSS v3.1 Published 2020-07-06
Fix available
A fix is available. Upgrade to 4.10.17 / 4.11.11 or later.
See remediation →
71/100
Remediation priority · Elevated
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
A use-after-free flaw was found in all samba LDAP server versions before 4.10.17, before 4.11.11, before 4.12.4 used in a AC DC configuration. A Samba LDAP user could use this flaw to crash samba.

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 · moderate confidence

Use-after-free vulnerability in Samba LDAP server affecting Active Directory Domain Controller configurations. Authenticated LDAP users can trigger a crash via the memory corruption flaw in versions before 4.10.17, 4.11.11, and 4.12.4.

MitigationUpgrade Samba to version 4.10.17 or later, 4.11.11 or later, or 4.12.4 or later. Plan maintenance window for DC upgrade to minimize disruption.

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:= 18.04= 19.10= 20.04
FedoraOperating system
Affected:= 31
SambaApplication
Affected:>= 4.5.0, < 4.10.17>= 4.11.0, < 4.11.11>= 4.12.0, < 4.12.4
LeapOperating system
Affected:= 15.1= 15.2

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Verify Samba is installed
    Run 'dpkg -l | grep samba' (Debian/Ubuntu) or 'rpm -qa | grep samba' (RHEL/Fedora) or check for /usr/sbin/smbd
    Affected if Samba is not installed, then not affected. If installed, proceed to next check.
  2. Determine installed Samba version
    Run 'samba --version' or 'smbd --version' to obtain the exact version number
    Affected if Version is less than 4.10.17, or between 4.11.0-4.11.10, or between 4.12.0-4.12.3, then vulnerable. Otherwise, not affected.
  3. Confirm LDAP server is running
    Check for active LDAP-related processes: 'ps aux | grep ldap' or 'systemctl status slapd' (OpenLDAP) or look for samba 'ldap' processes
    Affected if LDAP server daemon is not running, then not affected by this specific LDAP server flaw.
  4. Check if configured as Active Directory Domain Controller
    Examine smb.conf for 'server role = active directory domain controller' or run 'samba-tool domain info 127.0.0.1' to query AD status
    Affected if System is NOT configured as an AD DC, then not affected. The flaw specifically targets AD DC configurations.

System is affected only if Samba version falls within the vulnerable ranges AND the LDAP server is active AND the system is configured as an Active Directory Domain Controller.

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.10.17 / 4.11.11 / 4.12.4 or later
Fixed in 4.10.174.11.114.12.4
Interim mitigation

Upgrade Samba to version 4.10.17 or later, 4.11.11 or later, or 4.12.4 or later. Plan maintenance window for DC upgrade to minimize disruption.

Fix this in Ubuntu Linux Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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