# CVE-2015-7976: Command injection in n/a

> Attackers can execute arbitrary commands via crafted filenames in the ntpq saveconfig command due to improper input filtering.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Jan 2017
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-7976, GHSA-gh77-qwr7-pqm7, UBUNTU-CVE-2015-7976

## What is CVE-2015-7976?

CVE-2015-7976 is a medium-severity command injection vulnerability in Ntp Ntp, published on 30 Jan 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The ntpq saveconfig command in NTP 4.1.2, 4.2.x before 4.2.8p6, 4.3, 4.3.25, 4.3.70, and 4.3.77 does not properly filter special characters, which allows attackers to cause unspecified impact via a crafted filename.

Weakness: CWE-254

## Which versions are affected by CVE-2015-7976?

It affects 10 products.


Products: Novell Suse Openstack Cloud, Ntp Ntp, Opensuse Leap, Opensuse Opensuse, Suse Linux Enterprise Debuginfo, Suse Linux Enterprise Desktop, Suse Linux Enterprise Server, Suse Manager, Suse Manager Proxy, Suse Suse Linux Enterprise Server.

## How do I fix CVE-2015-7976?

Upgrade to a fixed version.

## Is CVE-2015-7976 being exploited?

There is no known exploitation of CVE-2015-7976 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-7976 and fix it if it is affected.

What it is: CVE-2015-7976 is a medium-severity command injection vulnerability in Ntp Ntp, published on 30 Jan 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-7976 in the wild and no public exploit code.

Affected product: Ntp Ntp. 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-2015-7976/ (Markdown: https://insights.sbomify.com/CVE-2015-7976/index.md)
```

## Sources

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

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