# CVE-2018-10900: Command injection in networkmanager-vpnc

> An attacker can inject a password helper parameter to execute arbitrary commands as root via the NetworkManager VPNC plugin.

- **Severity:** High 8.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/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:** 26 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-10900, DLA-1454-1, DSA-4253-1, GHSA-6cmp-3578-qc4p, SUSE-SU-2018:2297-1, UBUNTU-CVE-2018-10900, openSUSE-SU-2024:10604-1

## What is CVE-2018-10900?

CVE-2018-10900 is a high-severity command injection vulnerability in Debian Debian Linux, published on 26 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Network Manager VPNC plugin (aka networkmanager-vpnc) before version 1.2.6 is vulnerable to a privilege escalation attack. A new line character can be used to inject a Password helper parameter into the configuration data passed to VPNC, allowing an attacker to execute arbitrary commands as root.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2018-10900?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `NetworkManager-vpnc` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 1.0.8-8.4.2 |
| `NetworkManager-vpnc` | SUSE:Linux Enterprise Workstation Extension 12 SP3 | All versions | 1.0.8-8.4.2 |

Products: Debian Debian Linux, Gnome Network Manager Vpnc.

## How do I fix CVE-2018-10900?

Apply the vendor's patch.

## Is CVE-2018-10900 being exploited?

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

Public exploit code:

- Network Manager VPNC Username Privilege Escalation (metasploit)
- Network Manager VPNC 1.2.6 - 'Username' Local Privilege Escalation (Metasploit) (exploitdb)
- Network Manager VPNC 1.2.6 - 'Username' Local Privilege Escalation (Metasploit) (exploitdb)

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

What it is: CVE-2018-10900 is a high-severity command injection vulnerability in Debian Debian Linux, published on 26 Jul 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-2018-10900 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-2018-10900/ (Markdown: https://insights.sbomify.com/CVE-2018-10900/index.md)
```

## Sources

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

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