# CVE-2014-9293: Weak cryptography in n/a

> Remote attackers can defeat NTP cryptographic protections via brute-force due to improper key generation when no auth key is configured.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Dec 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-9293, GHSA-39gg-qjj7-qm8m, UBUNTU-CVE-2014-9293

## What is CVE-2014-9293?

CVE-2014-9293 is a high-severity vulnerability in Ntp Ntp, published on 20 Dec 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The config_auth function in ntpd in NTP before 4.2.7p11, when an auth key is not configured, improperly generates a key, which makes it easier for remote attackers to defeat cryptographic protection mechanisms via a brute-force attack.

## Which versions are affected by CVE-2014-9293?

It affects 1 product.


Products: Ntp Ntp.

## How do I fix CVE-2014-9293?

Upgrade to a fixed version.

## Is CVE-2014-9293 being exploited?

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

## Other vulnerabilities in Ntp Ntp

- [CVE-2018-12327](https://insights.sbomify.com/CVE-2018-12327/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-6460](https://insights.sbomify.com/CVE-2017-6460/): Memory corruption in n/a (high 8.8)
- [CVE-2019-11331](https://insights.sbomify.com/CVE-2019-11331/): Other in n/a (high 8.1)
- [CVE-2017-6451](https://insights.sbomify.com/CVE-2017-6451/): Memory corruption in n/a (high 7.8)
- [CVE-2017-6452](https://insights.sbomify.com/CVE-2017-6452/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-9293 and fix it if it is affected.

What it is: CVE-2014-9293 is a high-severity vulnerability in Ntp Ntp, published on 20 Dec 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-9293 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-2014-9293/ (Markdown: https://insights.sbomify.com/CVE-2014-9293/index.md)
```

## Sources

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

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