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

> Unauthenticated attackers can access sensitive logs and design files via exposed Apache directory indexing on the 3D printer.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2019
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2mrg-vqm4-vxr2

## What is CVE-2014-9699?

CVE-2014-9699 is a high-severity vulnerability in n/a, published on 24 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The MakerBot Replicator 5G printer runs an Apache HTTP Server with directory indexing enabled. Apache logs, system logs, design files (i.e., a history of print files), and more are exposed to unauthenticated attackers through this HTTP server.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Makerbot Replicator 5th Generation Firmware.

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

No fix has been published for CVE-2014-9699 yet. Limit exposure of the affected software until one is available.

## Is CVE-2014-9699 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-9699 is a high-severity vulnerability in n/a, published on 24 Jun 2019. 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-9699 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-9699/ (Markdown: https://insights.sbomify.com/CVE-2014-9699/index.md)
```

## Sources

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

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