CVE-2022-3437
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 · uneditedA heap-based buffer overflow vulnerability was found in Samba within the GSSAPI unwrap_des() and unwrap_des3() routines of Heimdal. The DES and Triple-DES decryption routines in the Heimdal GSSAPI library allow a length-limited write buffer overflow on malloc() allocated memory when presented with a maliciously small packet. This flaw allows a remote user to send specially crafted malicious data to the application, possibly resulting in a denial of service (DoS) attack.
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 confidenceHeap-based buffer overflow in Samba's Heimdal GSSAPI library in the unwrap_des() and unwrap_des3() DES/Triple-DES decryption routines. When processing a maliciously small packet, the length validation allows a write beyond the allocated malloc() buffer boundaries, leading to potential denial of 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= 36= 37>= 4.0.0, < 4.15.11>= 4.16.0, < 4.16.6>= 4.17.0, < 4.17.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if Samba is installedRun 'smbd --version' or 'samba --version' to get the Samba version. On Fedora/RHEL, also run 'rpm -q samba'Affected if Samba is installed and the version falls within 4.0.0 to 4.15.10, 4.16.0 to 4.16.5, or 4.17.0 to 4.17.1
-
Confirm the vulnerable code path existsVerify the Heimdal GSSAPI library is present. Check for existence of the file libgssapi or equivalent GSSAPI library shipped with Samba in the Samba library directoryAffected if The Heimdal GSSAPI library with DES/3DES support is present in the Samba installation
-
Check if DES/3DES is enabled in GSSAPI configurationInspect /etc/krb5.conf and /etc/samba/smb.conf for any configuration that explicitly enables DES or 3DES encryption types (look for 'des-cbc-crc', 'des-cbc-md5', 'des3-cbc-sha1' or similar in encryption types settings)Affected if DES or 3DES encryption types are explicitly listed as enabled in the Kerberos or Samba configuration files
-
Verify network exposure of Samba servicesCheck if smbd, winbind, or other Samba services are listening on network interfaces by running 'netstat -tulpn | grep -E "smbd|winbind"' or 'ss -tulpn | grep -E "smbd|winbind"'Affected if Samba services are bound to network interfaces and accessible from the network
You are affected if Samba is installed with a version in the vulnerable ranges AND DES/3DES support is enabled in your GSSAPI/Kerberos configuration, exposing the vulnerable decryption routines.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.15.114.16.64.17.2
Update Samba to the version containing the fix. If immediate patching is not possible, consider disabling DES/3DES in the GSSAPI configuration or restricting network access to affected services until the patch can be applied.
Samba 4.17.11 (or latest 4.17.x) - alternatively 4.16.11 (4.16.x) or 4.15.13 (4.15.x) depending on branch
- 1. Check current Samba version: smbd --version or rpm -q samba
- 2. For Samba 4.0.0 to 4.15.x: Upgrade to Samba 4.15.11 or later (recommended: 4.15.13 or latest 4.15.x)
- 3. For Samba 4.16.0 to 4.16.x: Upgrade to Samba 4.16.6 or later (recommended: 4.16.11 or latest 4.16.x)
- 4. For Samba 4.17.0 to 4.17.2: Upgrade to Samba 4.17.2 or later (recommended: 4.17.11 or latest 4.17.x)
- 5. On Fedora systems: Run 'dnf update samba' to apply available security patches
- 6. Restart Samba services after upgrade: 'systemctl restart smb nmb'
- 7. Verify the new version is running: smbd --version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3437 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-3437 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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