# CVE-2014-5377: Information disclosure in n/a

> Remote attackers can obtain user account credentials by sending a direct request to the ReadUsersFromMasterServlet endpoint.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/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:** 4 Sep 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mj2h-f2r8-7855

## What is CVE-2014-5377?

CVE-2014-5377 is a medium-severity vulnerability in n/a, published on 4 Sep 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ReadUsersFromMasterServlet in ManageEngine DeviceExpert before 5.9 build 5981 allows remote attackers to obtain user account credentials via a direct request.

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

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

It affects 1 product.


Products: Manageengine Device Expert.

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

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

## Is CVE-2014-5377 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-5377 exists.

Public exploit code:

- ManageEngine DeviceExpert 5.9 - User Credential Disclosure (exploitdb)
- ManageEngine DeviceExpert User Credentials (metasploit)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-5377 is a medium-severity vulnerability in n/a, published on 4 Sep 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-5377 exists.

Affected product: n/a. 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-5377/ (Markdown: https://insights.sbomify.com/CVE-2014-5377/index.md)
```

## Sources

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

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