dbcve.org
Enterprise LinuxOperating system · Redhat

CVE-2022-2127

MEDIUM · 5.9 CVSS v3.1 Published 2023-07-20
Fix available
A fix is available. Upgrade to 4.16.10 / 4.17.9 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges 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
An out-of-bounds read vulnerability was found in Samba due to insufficient length checks in winbindd_pam_auth_crap.c. When performing NTLM authentication, the client replies to cryptographic challenges back to the server. These replies have variable lengths, and Winbind fails to check the lan manager response length. When Winbind is used for NTLM authentication, a maliciously crafted request can trigger an out-of-bounds read in Winbind, possibly resulting in a crash.

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

Out-of-bounds read vulnerability in Samba's Winbind service due to missing length validation on NTLM authentication responses. When processing NTLM authentication, Winbind fails to check the lan manager response length before accessing the buffer, allowing a malicious client to trigger reads beyond buffer boundaries.

MitigationApply Samba security updates that address the bounds checking in winbindd_pam_auth_crap.c; if patches are unavailable, restrict NTLM authentication or limit network access to the Winbind service.

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
Enterprise LinuxOperating system
Affected:= 6.0= 7.0= 8.0= 9.0
FedoraOperating system
Affected:= 37= 38
Debian LinuxOperating system
Affected:= 12.0
SambaApplication
Affected:>= 4.16.0, < 4.16.10>= 4.17.0, < 4.17.9>= 4.18.0, < 4.18.4

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

CVSS:3.1/AV:N/AC:H/PR:N/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. Identify installed Samba version
    Run 'smbd --version' or 'rpm -q samba' (RHEL/Fedora) or 'dpkg -l samba' (Debian) to determine the Samba version number
    Affected if Version falls within 4.16.0-4.16.9, 4.17.0-4.17.8, or 4.18.0-4.18.3
  2. Verify winbind service is running
    Run 'ps aux | grep winbind' or 'systemctl status winbind' (or 'smb' service depending on distribution) to check if the winbind daemon is active
    Affected if winbindd process is running and handling authentication requests
  3. Confirm NTLM authentication is permitted
    Check Samba configuration: review 'security' and 'ntlm auth' settings in /etc/samba/smb.conf. Also check if domain trusts or legacy auth that use NTLM are in use
    Affected if NTLM authentication is enabled in the configuration or the system relies on NTLM-based domain authentication
  4. Check for signs of the vulnerable code path
    Review winbind logs (/var/log/samba/log.winbindd) for NTLM authentication attempts; use 'wbinfo -u' or 'wbinfo -a' to test NTLM authentication if winbind is active
    Affected if NTLM authentication requests are being processed by winbind service

You are affected if Samba versions 4.16.x (before 4.16.10), 4.17.x (before 4.17.9), or 4.18.x (before 4.18.4) are installed AND the winbind service is running with NTLM authentication enabled or in use.

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.9 / 4.18.4 or later
Fixed in 4.16.104.17.94.18.4
Interim mitigation

Apply Samba security updates that address the bounds checking in winbindd_pam_auth_crap.c; if patches are unavailable, restrict NTLM authentication or limit network access to the Winbind service.

Recommended fix High confidence

Samba 4.16.10, 4.17.9, or 4.18.4 (or later respective minor releases)

  1. 1. Identify the currently installed Samba version using: rpm -qa | grep samba or dpkg -l | grep samba
  2. 2. For RHEL/CentOS/Enterprise Linux systems: Run 'yum update samba' or 'dnf update samba' to apply the latest vendor security updates
  3. 3. For Fedora systems: Run 'dnf update samba' to apply the latest vendor security updates
  4. 4. For Debian systems: Run 'apt-get update && apt-get upgrade samba' to apply the latest vendor security updates
  5. 5. If using source-built Samba: Download and install Samba 4.16.10 or later, 4.17.9 or later, or 4.18.4 or later from samba.org
  6. 6. After updating, restart the winbind service using: systemctl restart winbind (or systemctl restart smbd for some distributions)
  7. 7. Verify the new Samba version is installed: smbstatus --version or winbindd --version
Caveat Upgrading Samba may require adjustments to smb.conf or related configurations; ensure to review release notes for any configuration changes between versions

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

Fix this in Enterprise Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
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,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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