# CVE-2017-0358: ntfs-3g: Modprobe influence vulnerability via environment variables

> Local attackers can escalate privileges to root by exploiting environment variable handling in the NTFS-3G driver when executing modprobe.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Apr 2018
- **Updated:** 4 Dec 2025
- **Also known as:** DEBIAN-CVE-2017-0358, DLA-815-1, DSA-3780-1, GHSA-vghw-r4fc-pgpf, SUSE-SU-2018:2070-1, SUSE-SU-2018:3587-1, SUSE-SU-2018:3587-2, UBUNTU-CVE-2017-0358, USN-3182-1

## What is CVE-2017-0358?

CVE-2017-0358 is a high-severity vulnerability in Debian Debian Linux, published on 13 Apr 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Jann Horn of Google Project Zero discovered that NTFS-3G, a read-write NTFS driver for FUSE, does not scrub the environment before executing modprobe with elevated privileges. A local user can take advantage of this flaw for local root privilege escalation.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2017-0358?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ntfs-3g_ntfsprogs` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 2013.1.13-5.3.1 |
| `ntfs-3g_ntfsprogs` | SUSE:Linux Enterprise Desktop 12 SP4 | All versions | 2013.1.13-5.3.1 |
| `ntfs-3g` | SUSE:Linux Enterprise Software Development Kit 11 SP4 | All versions | 2011.4.12-0.9.3.1 |
| `ntfs-3g_ntfsprogs` | SUSE:Linux Enterprise Software Development Kit 12 SP3 | All versions | 2013.1.13-5.3.1 |
| `ntfs-3g_ntfsprogs` | SUSE:Linux Enterprise Software Development Kit 12 SP4 | All versions | 2013.1.13-5.3.1 |
| `ntfs-3g_ntfsprogs` | SUSE:Linux Enterprise Workstation Extension 12 SP3 | All versions | 2013.1.13-5.3.1 |
| `ntfs-3g_ntfsprogs` | SUSE:Linux Enterprise Workstation Extension 12 SP4 | All versions | 2013.1.13-5.3.1 |

Products: Debian Debian Linux, Tuxera Ntfs-3g.

## How do I fix CVE-2017-0358?

Apply the vendor's patch.

## Is CVE-2017-0358 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-0358 exists.

Public exploit code:

- Debian/Ubuntu ntfs-3g Local Privilege Escalation (metasploit)
- ntfs-3g (Debian 9) - Local Privilege Escalation (exploitdb)
- ntfs-3g - Unsanitized modprobe Environment Privilege Escalation (exploitdb)
- https://github.com/Wangsafz/cve-2017-0358.sh (github_poc): https://github.com/Wangsafz/cve-2017-0358.sh

## 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-0358 and fix it if it is affected.

What it is: CVE-2017-0358 is a high-severity vulnerability in Debian Debian Linux, published on 13 Apr 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-0358 exists.

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-0358/ (Markdown: https://insights.sbomify.com/CVE-2017-0358/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-0358
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-0358
- OSV: https://osv.dev/vulnerability/CVE-2017-0358

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-0358/
Summaries are generated and may contain mistakes; the official description above is the record.