CVE-2014-6038 in the critical feed json
Zoho ManageEngine EventLog Analyzer versions 7 through 9.9 build 9002 have a database Information Disclosure Vulnerability.
published 2020-01-13 6 y ago modified 2026-06-17 4 mo ago also EUVD-2014-5926
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 72.8%
- EPSS 72.8% chance of exploitation in 30 days, percentile 99.4%
- public exploits
- 2
- Metasploit, Exploit-DB
Summary
Zoho ManageEngine EventLog Analyzer versions 7 through 9.9 build 9002 have a database Information Disclosure Vulnerability. Fixed in EventLog Analyzer 10.0 Build 10000.
Timeline
- First public exploit (Metasploit auxiliary/gather/eventlog_cred_disclosure)
- Published
Exploit prediction
72.76% chance of exploitation in the next 30 days, higher than 99.4% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit auxiliary/gather/eventlog_cred_disclosure ManageEngine Eventlog Analyzer Managed Hosts Administrator Credential Disclosure metasploit auxiliary, normal rank, 2014-11-05
- EDB-43893 ManageEngine EventLog Analyzer - Multiple Vulnerabilities (2) webapps, 2014-11-05
- packetstormsecurity.com http://packetstormsecurity.com/files/128996/ManageEngine-EventLog-Analyzer-SQL-Credential-Disclosure.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
packetstormsecurity.com
/files/128996/ManageEngine-EventLog-Analyzer-SQL-Credential-Disclosure.html
exploit, third-party-advisory, vdb-entry
-
securityfocus.com
/bid/70959
third-party-advisory, vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/98540
vdb-entry
-
seclists.org
/fulldisclosure/2014/Nov/12
mailing-list, third-party-advisory
Sources
- CVE List CVE-2014-6038
- NVD CVE-2014-6038
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.