# CVE-2019-10218: Path traversal in samba > A malicious Samba server can trick the client into accessing or creating files outside the intended directory via path traversal. - **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 6 Nov 2019 - **Updated:** 4 Aug 2024 - **Also known as:** ALPINE-CVE-2019-10218, DEBIAN-CVE-2019-10218, ECHO-5bf5-38e9-da43, GHSA-mjrv-7h6w-94x4, SUSE-SU-2019:14202-1, SUSE-SU-2019:2875-1, SUSE-SU-2019:2890-1, SUSE-SU-2019:2893-1, UBUNTU-CVE-2019-10218 ## What is CVE-2019-10218? CVE-2019-10218 is a medium-severity path traversal vulnerability in Fedoraproject Fedora, published on 6 Nov 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description A 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. Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2019-10218? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `samba` | SUSE:Enterprise Storage 5 | All versions | 4.6.16+git.169.064abe062be-3.46.1 | | `samba` | SUSE:HPE Helion OpenStack 8 | All versions | 4.6.16+git.169.064abe062be-3.46.1 | | `samba` | SUSE:Linux Enterprise Desktop 12 SP4 | All versions | 4.6.16+git.169.064abe062be-3.46.1 | | `samba` | SUSE:Linux Enterprise High Availability Extension 12 SP1 | All versions | 4.2.4-28.36.1 | | `samba` | SUSE:Linux Enterprise High Availability Extension 12 SP2 | All versions | 4.4.2-38.28.1 | | `samba` | SUSE:Linux Enterprise High Availability Extension 12 SP3 | All versions | 4.6.16+git.169.064abe062be-3.46.1 | | `samba` | SUSE:Linux Enterprise High Availability Extension 12 SP4 | All versions | 4.6.16+git.169.064abe062be-3.46.1 | | `samba` | SUSE:Linux Enterprise Point of Sale 11 SP3 | All versions | 3.6.3-94.23.1 | | `samba-doc` | SUSE:Linux Enterprise Point of Sale 11 SP3 | All versions | 3.6.3-94.23.1 | | `samba` | SUSE:Linux Enterprise Server 11 SP4-LTSS | All versions | 3.6.3-94.23.1 | | `samba-doc` | SUSE:Linux Enterprise Server 11 SP4-LTSS | All versions | 3.6.3-94.23.1 | | `samba` | SUSE:Linux Enterprise Server 12 SP1-LTSS | All versions | 4.2.4-28.36.1 | | `samba` | SUSE:Linux Enterprise Server 12 SP2-BCL | All versions | 4.2.4-28.36.1 | | `samba` | SUSE:Linux Enterprise Server 12 SP2-BCL | All versions | 4.4.2-38.28.1 | | `samba` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 4.2.4-28.36.1 | | `samba` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 4.4.2-38.28.1 | | `samba` | SUSE:Linux Enterprise Server 12 SP3-BCL | All versions | 4.6.16+git.169.064abe062be-3.46.1 | | `samba` | SUSE:Linux Enterprise Server 12 SP3-LTSS | All versions | 4.6.16+git.169.064abe062be-3.46.1 | | `samba` | SUSE:Linux Enterprise Server 12 SP4 | All versions | 4.6.16+git.169.064abe062be-3.46.1 | | `samba` | SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 4.2.4-28.36.1 | | `samba` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 4.2.4-28.36.1 | | `samba` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 4.4.2-38.28.1 | | `samba` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 4.6.16+git.169.064abe062be-3.46.1 | | `samba` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 4.6.16+git.169.064abe062be-3.46.1 | | `samba` | SUSE:Linux Enterprise Software Development Kit 12 SP4 | All versions | 4.6.16+git.169.064abe062be-3.46.1 | | `samba` | SUSE:OpenStack Cloud 7 | All versions | 4.2.4-28.36.1 | | `samba` | SUSE:OpenStack Cloud 7 | All versions | 4.4.2-38.28.1 | | `samba` | SUSE:OpenStack Cloud 8 | All versions | 4.6.16+git.169.064abe062be-3.46.1 | | `samba` | SUSE:OpenStack Cloud Crowbar 8 | All versions | 4.6.16+git.169.064abe062be-3.46.1 | Products: Fedoraproject Fedora, Samba Samba. ## How do I fix CVE-2019-10218? Upgrade to a fixed version. ## Is CVE-2019-10218 being exploited? There is no known exploitation of CVE-2019-10218 in the wild and no public exploit code. ## Other vulnerabilities in Fedoraproject Fedora - [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild) - [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild) - [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-10218 and fix it if it is affected. What it is: CVE-2019-10218 is a medium-severity path traversal vulnerability in Fedoraproject Fedora, published on 6 Nov 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2019-10218 in the wild and no public exploit code. Affected product: Fedoraproject Fedora. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2019-10218/ (Markdown: https://insights.sbomify.com/CVE-2019-10218/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-10218 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-10218 - OSV: https://osv.dev/vulnerability/CVE-2019-10218 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-10218/ Summaries are generated and may contain mistakes; the official description above is the record.