# CVE-2014-2960: Information disclosure in Vision Critical before 2014-05-30

> Attackers can read arbitrary files, including images and configuration files, from the Vision Critical platform.

- **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:** 10 Apr 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-486g-3323-7948

## What is CVE-2014-2960?

CVE-2014-2960 is a high-severity vulnerability in Vision Critical before 2014-05-30, published on 10 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vision Critical before 2014-05-30 allows attackers to read arbitrary files via unspecified vectors, as demonstrated by image files and configuration files.

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

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

It affects 1 product.


Products: Visioncritical Vision Critical.

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

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

## Is CVE-2014-2960 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-2960 is a high-severity vulnerability in Vision Critical before 2014-05-30, published on 10 Apr 2017. 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-2960 in the wild and no public exploit code.

Affected product: Vision Critical before 2014-05-30. 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-2960/ (Markdown: https://insights.sbomify.com/CVE-2014-2960/index.md)
```

## Sources

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

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