FreeBSDOperating system

CVE-2017-15037

HIGH · 8.1 CVSS v3.0 Published 2017-10-05
Fix available
A fix is available. Upgrade to after 11.1 or later.
See remediation →
90/100
Remediation priority · Urgent
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
In FreeBSD through 11.1, the smb_strdupin function in sys/netsmb/smb_subr.c has a race condition with a resultant out-of-bounds read, because it can cause t2p->t_name strings to lack a final '\0' character.

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

In FreeBSD through 11.1, the smb_strdupin function in sys/netsmb/smb_subr.c contains a race condition that can cause t2p->t_name strings to lack a null terminator ('\0'), resulting in an out-of-bounds read vulnerability.

MitigationApply the FreeBSD security patch for CVE-2017-15037 which fixes the race condition in smb_strdupin to ensure proper string termination; upgrade to FreeBSD 11.1 or later if the patch is not available for earlier versions.

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
FreeBSDOperating system
Affected:<= 11.1

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

CVSS:3.0/AV:N/AC:H/PR:N/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. Check FreeBSD version
    Run `freebsd-version` or `uname -r` to determine the installed FreeBSD version
    Affected if The version is 11.1 or earlier (e.g., 11.0, 10.x, 9.x)
  2. Verify SMB kernel module is loaded
    Run `kldstat | grep netsmb` to check if the SMB kernel module is loaded
    Affected if The netsmb module appears in the output, indicating SMB support is active
  3. Check for active SMB configurations
    Run `ls /etc/nsmb.conf` or check for SMB shares in /etc/fstab or via `mount | grep smbfs`
    Affected if SMB configurations or mounts exist, indicating SMB functionality is in use

The system is potentially affected if it runs FreeBSD 11.1 or earlier AND has the SMB (netsmb) module loaded or SMB functionality configured.

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 a release after 11.1
Interim mitigation

Apply the FreeBSD security patch for CVE-2017-15037 which fixes the race condition in smb_strdupin to ensure proper string termination; upgrade to FreeBSD 11.1 or later if the patch is not available for earlier versions.

Fix this in FreeBSD Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-15037 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-15037 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