CVE-2014-2933
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 · uneditedDirectory traversal vulnerability in dirmng/index.php in Caldera 9.20 allows remote attackers to access arbitrary directories via a crafted pathname.
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 · high confidenceDirectory traversal vulnerability in Caldera 9.20's dirmng/index.php allows remote attackers to access arbitrary directories on the server by using crafted pathname sequences (such as ../) in HTTP requests, potentially exposing sensitive file system contents.
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= 9.20CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/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 Caldera version 9.20 is installedLocate and inspect the Caldera installation directory, check version file or package metadata that indicates the installed versionAffected if The installed version is Caldera 9.20 exactly
-
Confirm dirmng/index.php existsCheck for the presence of the file dirmng/index.php within the Caldera web application root directoryAffected if The file dirmng/index.php exists in the web application directory
-
Verify web server exposes Caldera applicationDetermine if a web server (Apache, Nginx, etc.) is running and configured to serve the Caldera application files, including the dirmng directoryAffected if The Caldera web application and its dirmng module are accessible over HTTP/HTTPS
-
Test dirmng endpoint accessibilityAttempt an HTTP request to the dirmng/index.php endpoint (e.g., GET /dirmng/index.php) and confirm it returns a valid response rather than a 404 errorAffected if The dirmng/index.php endpoint is reachable and responds to HTTP requests
A user is affected if Caldera version 9.20 is installed with the dirmng/index.php file accessible via a running web server, allowing potential directory traversal via ../ sequences in requests to that endpoint.
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 dataImplement strict input validation and path sanitization in dirmng/index.php to ensure all path inputs are validated against an allowed base directory and reject any sequences that could enable directory traversal.
- Consultation3.0 h
- Implementation4.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,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2933 — 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-2933 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