CVE-2014-8678
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 · uneditedThe ConfigSaveServlet servlet in ManageEngine OpUtils before build 71024 allows remote attackers to "disclose" files via a crafted filename, related to "saveFile."
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 confidenceThe ConfigSaveServlet in ManageEngine OpUtils prior to build 71024 contains an arbitrary file disclosure vulnerability. Attackers can exploit the 'saveFile' parameter by providing a crafted filename to read sensitive files from the server's filesystem. This is a remote, unauthenticated vulnerability allowing file contents to be returned in the servlet response.
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<= 7.0CVSS 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
- Complete
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:C/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 ManageEngine OpUtils is installedCheck for OpUtils processes running on the system (look for java processes related to OpUtils) or check if port 8080 or 8443 is listening with OpUtils web interfaceAffected if ManageEngine OpUtils is found running on the system
-
Determine the OpUtils build numberAccess the OpUtils web interface and navigate to Help > About, or check the build.info/version file in the OpUtils installation directoryAffected if The build number is 71024 or lower, or the version is 7.0 or lower
-
Confirm the ConfigSaveServlet is accessibleCheck if the URL pattern /ConfigSaveServlet is reachable on the OpUtils web server (e.g., http://target:8080/ConfigSaveServlet)Affected if The ConfigSaveServlet endpoint responds to requests
-
Check if the saveFile parameter is functionalSend a crafted GET or POST request to ConfigSaveServlet with a test filename parameter (e.g., saveFile=../test.txt) and observe if file content is returnedAffected if Arbitrary file content can be retrieved through the saveFile parameter without authentication
A user is affected if ManageEngine OpUtils build 71024 or lower is running and the ConfigSaveServlet is accessible, allowing unauthenticated file disclosure via the saveFile parameter.
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 dataUpgrade ManageEngine OpUtils to build 71024 or later. If immediate patching is not feasible, restrict network access to the ConfigSaveServlet endpoint or disable the application's file upload/save functionality until the upgrade can be deployed.
- Consultation2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-8678 — 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-8678 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