CVE-2014-0344
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 · uneditedProperties.do in ZOHO ManageEngine OpStor before build 8500 does not properly check privilege levels, which allows remote authenticated users to obtain Admin access by using the name parameter in conjunction with a true value of the edit parameter.
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 confidenceThis is a privilege escalation vulnerability in ZOHO ManageEngine OpStor's Properties.do component. The endpoint fails to properly validate user privilege levels, allowing any authenticated user to obtain Admin access by manipulating the 'name' parameter alongside a 'true' value for the 'edit' parameter.
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<= 8.3CVSS 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
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/C:P/I:P/A:P
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.
-
Identify if ManageEngine OpStor is installedCheck for the presence of ManageEngine OpStor web application files in the web server directory, or look for the service running on typical ports (8080, 8090, etc.)Affected if The application is found running on the system
-
Check the installed OpStor version numberAccess the OpStor web interface login page or check the build/version information in the administration panel, typically found under Help or About sectionsAffected if The version is 8.3 or lower, or the build number is below 8500
-
Verify the Properties.do endpoint existsAttempt to access the URL pattern /servlet/com.manageengine.opstor.servlet.Properties.do or similar patterns under the OpStor web contextAffected if The endpoint responds to requests (indicates the vulnerable component is present)
-
Check for improper authorization on Properties.doLog in as a non-admin user and attempt to manipulate the 'name' parameter with 'edit=true' to access admin-level functionsAffected if A non-admin authenticated user can access admin functions through this endpoint
A user is affected if ManageEngine OpStor version 8.3 or lower is running and the Properties.do endpoint allows privilege escalation for authenticated non-admin users.
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 to ManageEngine OpStor build 8500 or later which addresses the improper privilege checking. Alternatively, implement proper authorization checks on the Properties.do endpoint to verify admin-level privileges before allowing configuration modifications.
- Consultation2.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0344 — 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-0344 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