FedoraOperating system · Fedoraproject
CVE-2019-10218
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 flaw was found in the samba client, all samba versions before samba 4.11.2, 4.10.10 and 4.9.15, where a malicious server can supply a pathname to the client with separators. This could allow the client to access files and folders outside of the SMB network pathnames. An attacker could use this vulnerability to create files outside of the current working directory using the privileges of the client user.
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 confidenceThe Samba client fails to properly validate pathnames returned by a server, allowing a malicious server to inject path separators that escape the intended SMB share boundaries. This path traversal vulnerability enables the server to cause the client to create or access files outside the designated network path using the authenticated user's privileges.
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
FedoraOperating system
= 29= 31< 4.9.15>= 4.10.0, < 4.10.10>= 4.11.0, < 4.11.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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check if Samba client is installedRun 'rpm -qa | grep -i samba' on Fedora or check installed packages on other Linux distributions. Look for packages like 'samba-client', 'libsmbclient', or 'smbclient'.Affected if No Samba client packages are installed, then the vulnerability does not apply.
-
Identify the exact Samba client versionRun 'rpm -qa | grep -i samba-client' and note the full version string (e.g., samba-client-4.11.2-1.fc31.x86_64).Affected if Version cannot be determined from installed packages.
-
Compare installed version against affected rangesFor Fedora: versions 4.9.x below 4.9.15, 4.10.x below 4.10.10, or 4.11.x below 4.11.2 are affected. For other Samba: versions < 4.9.15, >= 4.10.0 and < 4.10.10, or >= 4.11.0 and < 4.11.2 are affected.Affected if The installed Samba client version falls within any of these vulnerable ranges: < 4.9.15, >= 4.10.0 and < 4.10.10, or >= 4.11.0 and < 4.11.2.
-
Verify operating system version on FedoraRun 'cat /etc/fedora-release' or 'hostnamectl' to confirm the Fedora release number.Affected if Running Fedora 29 or 31 with an affected Samba client version increases urgency for remediation.
You are affected if the Samba client (smbclient or libsmbclient) is installed and its version is below 4.9.15, between 4.10.0 and 4.10.9, or between 4.11.0 and 4.11.1.
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.
From vendor data4.9.154.10.104.11.2
Upgrade Samba to version 4.11.2, 4.10.10, or 4.9.15 or later to patch the client-side path validation flaw.
Fix this in Fedora
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10218 — 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-2019-10218 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