# CVE-2014-3209: Information disclosure in n/a

> Local attackers can read private keys generated by ldns-keygen due to insecure file permissions based on the current umask.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **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:** 16 Nov 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-3209, GHSA-cc58-7rpr-73mr, MGASA-2014-0212, UBUNTU-CVE-2014-3209

## What is CVE-2014-3209?

CVE-2014-3209 is a low-severity vulnerability in n/a, published on 16 Nov 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The ldns-keygen tool in ldns 1.6.x uses the current umask to set the privileges of the private key, which might allow local users to obtain the private key by reading the file.

Weakness: CWE-264

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

It affects 1 product.


Products: Nlnetlabs Ldns.

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

Apply the vendor's patch.

## Is CVE-2014-3209 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-1000231](https://insights.sbomify.com/CVE-2017-1000231/): Use after free in n/a (critical 9.8)
- [CVE-2017-1000232](https://insights.sbomify.com/CVE-2017-1000232/): Use after free in n/a (critical 9.8)
- [CVE-2026-10846](https://insights.sbomify.com/CVE-2026-10846/): Insufficient verification that responses belong to a query (high 8.2)
- [CVE-2020-19861](https://insights.sbomify.com/CVE-2020-19861/): Information disclosure in n/a (high 7.5)
- [CVE-2011-3581](https://insights.sbomify.com/CVE-2011-3581/): Memory corruption in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-3209 is a low-severity vulnerability in n/a, published on 16 Nov 2014. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-3209 in the wild and no public exploit code.

Affected product: n/a. 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-3209/ (Markdown: https://insights.sbomify.com/CVE-2014-3209/index.md)
```

## Sources

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

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