# CVE-2017-7494: Samba Remote Code Execution > Attackers can upload and execute malicious shared libraries on writable Samba shares, leading to remote code execution. - **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Yes, since 30 Mar 2023 (CISA KEV), used in ransomware - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 30 May 2017 - **Updated:** 21 Oct 2025 - **Also known as:** ALPINE-CVE-2017-7494, AZL-110360, DEBIAN-CVE-2017-7494, DLA-951-1, DSA-3860-1, ECHO-a98d-272f-29e3, GHSA-453q-q3mp-9cq4, RHSA-2017:1270, RHSA-2017:1271, RHSA-2017:1272, RHSA-2017:1273, RHSA-2017:1390, SUSE-SU-2017:1391-1, SUSE-SU-2017:1392-1, SUSE-SU-2017:1393-1, SUSE-SU-2017:1396-1, UBUNTU-CVE-2017-7494, USN-3296-1 ## What is CVE-2017-7494? CVE-2017-7494 is a critical code injection vulnerability in Debian Debian Linux, published on 30 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Samba since version 3.5.0 and before 4.6.4, 4.5.10 and 4.4.14 is vulnerable to remote code execution vulnerability, allowing a malicious client to upload a shared library to a writable share, and then cause the server to load and execute it. Weakness: CWE-94 (Improper Control of Generation of Code) ## Which versions are affected by CVE-2017-7494? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libsmbclient` | Red Hat:enterprise_linux:6::client | All versions | 0:3.6.23-43.el6_9 | | `libsmbclient-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:3.6.23-43.el6_9 | | `samba` | Red Hat:enterprise_linux:6::client | All versions | 0:3.6.23-43.el6_9 | | `samba-client` | Red Hat:enterprise_linux:6::client | All versions | 0:3.6.23-43.el6_9 | | `samba-common` | Red Hat:enterprise_linux:6::client | All versions | 0:3.6.23-43.el6_9 | | `samba-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:3.6.23-43.el6_9 | | `samba-doc` | Red Hat:enterprise_linux:6::client | All versions | 0:3.6.23-43.el6_9 | | `samba-domainjoin-gui` | Red Hat:enterprise_linux:6::client | All versions | 0:3.6.23-43.el6_9 | | `samba-glusterfs` | Red Hat:enterprise_linux:6::client | All versions | 0:3.6.23-43.el6_9 | | `samba-swat` | Red Hat:enterprise_linux:6::client | All versions | 0:3.6.23-43.el6_9 | | `samba-winbind` | Red Hat:enterprise_linux:6::client | All versions | 0:3.6.23-43.el6_9 | | `samba-winbind-clients` | Red Hat:enterprise_linux:6::client | All versions | 0:3.6.23-43.el6_9 | | `samba-winbind-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:3.6.23-43.el6_9 | | `samba-winbind-krb5-locator` | Red Hat:enterprise_linux:6::client | All versions | 0:3.6.23-43.el6_9 | | `samba4` | Red Hat:enterprise_linux:6::client | All versions | 0:4.2.10-10.el6_9 | | `samba4-client` | Red Hat:enterprise_linux:6::client | All versions | 0:4.2.10-10.el6_9 | | `samba4-common` | Red Hat:enterprise_linux:6::client | All versions | 0:4.2.10-10.el6_9 | | `samba4-dc` | Red Hat:enterprise_linux:6::client | All versions | 0:4.2.10-10.el6_9 | | `samba4-dc-libs` | Red Hat:enterprise_linux:6::client | All versions | 0:4.2.10-10.el6_9 | | `samba4-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:4.2.10-10.el6_9 | | `samba4-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:4.2.10-10.el6_9 | | `samba4-libs` | Red Hat:enterprise_linux:6::client | All versions | 0:4.2.10-10.el6_9 | | `samba4-pidl` | Red Hat:enterprise_linux:6::client | All versions | 0:4.2.10-10.el6_9 | | `samba4-python` | Red Hat:enterprise_linux:6::client | All versions | 0:4.2.10-10.el6_9 | | `samba4-test` | Red Hat:enterprise_linux:6::client | All versions | 0:4.2.10-10.el6_9 | | `samba4-winbind` | Red Hat:enterprise_linux:6::client | All versions | 0:4.2.10-10.el6_9 | | `samba4-winbind-clients` | Red Hat:enterprise_linux:6::client | All versions | 0:4.2.10-10.el6_9 | | `samba4-winbind-krb5-locator` | Red Hat:enterprise_linux:6::client | All versions | 0:4.2.10-10.el6_9 | | `libsmbclient` | Red Hat:enterprise_linux:6::computenode | All versions | 0:3.6.23-43.el6_9 | | `libsmbclient-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:3.6.23-43.el6_9 | | `samba` | Red Hat:enterprise_linux:6::computenode | All versions | 0:3.6.23-43.el6_9 | | `samba-client` | Red Hat:enterprise_linux:6::computenode | All versions | 0:3.6.23-43.el6_9 | | `samba-common` | Red Hat:enterprise_linux:6::computenode | All versions | 0:3.6.23-43.el6_9 | | `samba-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:3.6.23-43.el6_9 | | `samba-doc` | Red Hat:enterprise_linux:6::computenode | All versions | 0:3.6.23-43.el6_9 | | `samba-domainjoin-gui` | Red Hat:enterprise_linux:6::computenode | All versions | 0:3.6.23-43.el6_9 | | `samba-glusterfs` | Red Hat:enterprise_linux:6::computenode | All versions | 0:3.6.23-43.el6_9 | | `samba-swat` | Red Hat:enterprise_linux:6::computenode | All versions | 0:3.6.23-43.el6_9 | | `samba-winbind` | Red Hat:enterprise_linux:6::computenode | All versions | 0:3.6.23-43.el6_9 | | `samba-winbind-clients` | Red Hat:enterprise_linux:6::computenode | All versions | 0:3.6.23-43.el6_9 | Products: Debian Debian Linux, Samba Samba. ## How do I fix CVE-2017-7494? Apply the vendor's patch. US federal agencies must fix it by 20 Apr 2023. ## Is CVE-2017-7494 being exploited? Yes. Attackers have exploited CVE-2017-7494 in the wild since at least 30 Mar 2023, including in ransomware campaigns. Public exploit code: - SambaCry exploit and vulnerable container (CVE-2017-7494) (github_poc): https://github.com/opsxcq/exploit-CVE-2017-7494 - Remote root exploit for the SAMBA CVE-2017-7494 vulnerability (github_poc): https://github.com/joxeankoret/CVE-2017-7494 - Proof-of-Concept exploit for CVE-2017-7494(Samba RCE from a writable share) (github_poc): https://github.com/betab0t/cve-2017-7494 - CVE-2017-7494 - Detection Scripts (github_poc): https://github.com/Waffles-2/SambaCry - It is a simple script to exploit RCE for Samba (CVE-2017-7494 ). (github_poc): https://github.com/brianwrf/SambaHunter - SambaCry (CVE-2017-7494) exploit for Samba | bind shell without Metasploit (github_poc): https://github.com/d3fudd/CVE-2017-7494_SambaCry ## Other vulnerabilities in Debian Debian Linux - [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild) - [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild) - [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild) - [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild) - [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2017-7494 and fix it if it is affected. What it is: CVE-2017-7494 is a critical code injection vulnerability in Debian Debian Linux, published on 30 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: Yes. Attackers have exploited CVE-2017-7494 in the wild since at least 30 Mar 2023, including in ransomware campaigns. Affected product: Debian Debian Linux. 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-2017-7494/ (Markdown: https://insights.sbomify.com/CVE-2017-7494/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2017-7494 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-7494 - OSV: https://osv.dev/vulnerability/CVE-2017-7494 --- From sbomify Insights: https://insights.sbomify.com/CVE-2017-7494/ Summaries are generated and may contain mistakes; the official description above is the record.