CVE-2014-2960
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedVision Critical before 2014-05-30 allows attackers to read arbitrary files via unspecified vectors, as demonstrated by image files and configuration files.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceVision Critical before 2014-05-30 contains an arbitrary file read vulnerability that allows unauthenticated attackers to read any file on the server file system, including sensitive configuration files, through unspecified vectors.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2014-05-30CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Vision Critical application is network accessibleDetermine if the Vision Critical web application is exposed on the network. Attempt to access the application's HTTP/HTTPS endpoints from an external or non-privileged network location. If the application responds to unauthenticated requests, it may be exploitable.Affected if The application is accessible over the network without authentication and runs a version dated on or before 2014-05-30
-
Identify installed Vision Critical versionLocate version information for the Vision Critical installation. Check for version files, about pages, or administrative interfaces that display the software version. Common locations include the application header/footer, /about endpoint, or configuration files within the application directory.Affected if The version displayed or stored is dated 2014-05-30 or earlier, or no version is displayed but the application build/release date falls on or before that threshold
-
Confirm lack of authentication requirement for file accessTest whether the application permits unauthenticated access to internal resources or functionality. Since CVE-2014-2960 allows unauthenticated file reads, verify that the application does not require login or session authentication to access core features.Affected if The application allows unauthenticated access to file-based functionality and the version is at or below the 2014-05-30 release date
-
Review application logs for suspicious file accessExamine server and application logs for unusual file read requests, particularly attempts to access system files such as /etc/passwd, configuration files, or other sensitive paths that would indicate exploitation attempts.Affected if Logs show anomalous file read requests from unauthenticated sources and the application version is at or below the affected threshold
A Vision Critical installation is affected if it is accessible over the network and runs any version dated on or before May 30, 2014.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate Vision Critical to version released after 2014-05-30 to obtain the vendor patch. If immediate patching is not possible, restrict network access to the application and implement file system access controls to limit the web server's read permissions to only necessary files.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2960 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-2960 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data