dbcve.org
SambaApplication

CVE-2023-0614

MEDIUM · 6.5 CVSS v3.1 Published 2023-04-03
Fix available
A fix is available. Upgrade to 4.16.10 / 4.17.7 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
The fix in 4.6.16, 4.7.9, 4.8.4 and 4.9.7 for CVE-2018-10919 Confidential attribute disclosure vi LDAP filters was insufficient and an attacker may be able to obtain confidential BitLocker recovery keys from a Samba AD DC.

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

An incomplete fix for CVE-2018-10919 allows authenticated attackers to query confidential BitLocker recovery keys through LDAP filters on Samba Active Directory Domain Controllers. The original confidential attribute disclosure vulnerability was not fully remediated in Samba versions 4.6.16, 4.7.9, 4.8.4, and 4.9.7.

MitigationUpgrade Samba to versions beyond the affected releases that contain the complete fix for CVE-2018-10919, or apply vendor-supplied patches that properly restrict LDAP filter access to confidential attributes like BitLocker recovery keys.

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
SambaApplication
Affected:>= 4.0.0, < 4.16.10>= 4.17.0, < 4.17.7= 4.18.0

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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, rpm -qa | grep samba) to determine installed Samba version
    Affected if Version is >= 4.0.0 and < 4.16.10, OR >= 4.17.0 and < 4.17.7, OR exactly 4.18.0
  2. Verify Samba is configured as Active Directory Domain Controller
    Check smb.conf for 'server role = active directory domain controller' or examine output of 'samba-tool domain info 127.0.0.1'
    Affected if Samba is running as an AD DC (this is required for the LDAP attribute exposure to occur)
  3. Confirm LDAP service is accessible
    Run 'ldapsearch -h localhost -p 389 -x' or check that port 389 is listening (netstat -tlnp | grep 389)
    Affected if LDAP is exposed and accepting connections (the vulnerability is exploited via LDAP filter queries)
  4. Test for exposure of confidential attributes
    Using an authenticated LDAP query (as any AD user), attempt to read attributes such as msTPM-OwnerInfo, or search for objects with 'objectClass=*' and BitLocker-related attributes. Example: ldapsearch -h localhost -p 389 -D 'CN=user,CN=Users,DC=domain,DC=com' -W -b 'DC=domain,DC=com' '*' | grep -i recovery
    Affected if Confidential BitLocker recovery keys or other confidential attributes (like msTPM-OwnerInfo) are returned in LDAP query results to authenticated users who should not have access

If Samba is running as an Active Directory Domain Controller with a version in the affected range and LDAP queries return confidential attributes like BitLocker recovery keys to standard authenticated users, the environment is vulnerable to CVE-2023-0614.

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.

dbcve · scoped
Upgrade available Upgrade to 4.16.10 / 4.17.7 or later
Fixed in 4.16.104.17.7
Interim mitigation

Upgrade Samba to versions beyond the affected releases that contain the complete fix for CVE-2018-10919, or apply vendor-supplied patches that properly restrict LDAP filter access to confidential attributes like BitLocker recovery keys.

Recommended fix High confidence

Samba 4.16.10+, 4.17.7+, or 4.18.1+ (latest stable release recommended)

  1. 1. Identify the currently installed Samba version using 'samba --version' or checking your package manager
  2. 2. Determine which branch of Samba you are running (4.16.x, 4.17.x, or 4.18.x)
  3. 3. For Samba 4.16.x users: upgrade to version 4.16.10 or later
  4. 4. For Samba 4.17.x users: upgrade to version 4.17.7 or later
  5. 5. For Samba 4.18.0 users: upgrade to version 4.18.1 or later
  6. 6. After upgrading, verify the new version is installed using 'samba --version'
  7. 7. Review Samba release notes for the security fix details
Caveat Minor - this is a security fix; review release notes for any configuration changes related to LDAP attribute filtering

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Samba Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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