CVE-2013-1814

NONECVSS 0.0Weaponized
0.0
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 74%
CISA-KEV: Not listedEPSS: 74%CVSS: —Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The users/get program in the User RPC API in Apache Rave 0.11 through 0.20 allows remote authenticated users to obtain sensitive information about all user accounts via the offset parameter, as demonstrated by discovering password hashes in the password field of a response.

CVSS v3
—
EG Score
0.0(none)
EG Risk
0
EG Risk 0/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses intrinsic severity with real-world exploitation and automatability, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. It is distinct from the 0–10 EG Score, which measures severity.

EPSS
99.4%
KEV
Not listed

Published

March 14, 2013

Last Modified

April 29, 2026

References (4)

Affected Packages

(3 across 1 ecosystem)
Maven(3)
PackageVulnerable rangeFixed inDependents
org.apache.rave:rave-core0.11 ... 0.20 (8 versions)0.20.1—
org.apache.rave:rave-portal-resources0.11 ... 0.20 (8 versions)0.20.1—
org.apache.rave:rave-web0.11 ... 0.20 (8 versions)0.20.1—

Data Freshness Timeline

(refreshed 12× in last 7d / 26× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 14:14 UTCEPSS rescore
  2. 2026-07-23 01:09 UTCEG score recompute▼ 7.20
  3. 2026-07-23 00:13 UTCEG score recompute▲ 7.20
  4. 2026-07-22 21:51 UTCEG score recompute
  5. 2026-07-22 14:04 UTCEPSS rescore
  6. 2026-07-22 14:04 UTCEPSS rescore
  7. 2026-07-20 17:03 UTCEPSS rescore
  8. 2026-07-20 17:03 UTCEPSS rescore
  9. 2026-07-19 14:27 UTCEPSS rescore
  10. 2026-07-19 14:27 UTCEPSS rescore
  11. 2026-07-19 02:25 UTCEPSS rescore
  12. 2026-07-19 02:25 UTCEPSS rescore
  13. 2026-07-15 16:54 UTCEPSS rescore
  14. 2026-07-15 16:54 UTCEPSS rescore
  15. 2026-07-15 01:56 UTCEPSS rescore
  16. 2026-07-13 06:08 UTCEPSS rescore
  17. 2026-07-11 08:23 UTCEPSS rescore
  18. 2026-07-06 02:19 UTCEPSS rescore
  19. 2026-07-06 02:19 UTCEPSS rescore
  20. 2026-07-04 06:27 UTCEPSS rescore
  21. 2026-07-01 15:02 UTCEPSS rescore
  22. 2026-06-30 23:19 UTCEPSS rescore
  23. 2026-06-30 23:19 UTCEPSS rescore
  24. 2026-06-28 14:03 UTCEPSS rescore
  25. 2026-06-27 03:05 UTCEPSS rescore
Show 34 more
  1. 2026-06-25 13:46 UTCEPSS rescore
  2. 2026-06-24 14:02 UTCEPSS rescore
  3. 2026-06-24 14:02 UTCEPSS rescore
  4. 2026-06-23 21:30 UTCEPSS rescore
  5. 2026-06-17 17:49 UTCEPSS rescore
  6. 2026-06-17 17:49 UTCEPSS rescore
  7. 2026-06-16 17:49 UTCEPSS rescore
  8. 2026-06-16 17:49 UTCEPSS rescore
  9. 2026-06-15 17:44 UTCEPSS rescore
  10. 2026-06-14 23:14 UTCEPSS rescore
  11. 2026-06-12 23:08 UTCEPSS rescore
  12. 2026-06-10 13:18 UTCEPSS rescore
  13. 2026-06-05 22:44 UTCEPSS rescore
  14. 2026-06-05 22:44 UTCEPSS rescore
  15. 2026-06-02 20:10 UTCEPSS rescore
  16. 2026-06-02 20:10 UTCEPSS rescore
  17. 2026-05-31 00:14 UTCEPSS rescore
  18. 2026-05-31 00:14 UTCEPSS rescore
  19. 2026-05-29 00:38 UTCEG score recompute
  20. 2026-05-28 13:42 UTCEPSS rescore
  21. 2026-05-28 13:42 UTCEPSS rescore
  22. 2026-05-28 13:42 UTCEPSS rescore
  23. 2026-05-27 13:38 UTCEPSS rescore
  24. 2026-05-27 13:38 UTCEPSS rescore
  25. 2026-05-26 07:16 UTCEPSS rescore
  26. 2026-05-26 07:16 UTCEPSS rescore
  27. 2026-05-22 21:15 UTCEPSS rescore
  28. 2026-05-22 21:15 UTCEPSS rescore
  29. 2026-05-22 21:15 UTCEPSS rescore
  30. 2026-05-21 22:39 UTCEPSS rescore
  31. 2026-05-20 22:37 UTCEPSS rescore
  32. 2026-05-20 22:37 UTCEPSS rescore
  33. 2026-05-18 21:29 UTCEPSS rescore
  34. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 Metasploit module) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-24744
    First seen Mar 13, 2013

    Apache Rave 0.11 < 0.20 - User Information Disclosure

    Open source ↗
  • Metasploitauxiliary/gather/apache_rave_creds✓ verified
    First seen Jan 1, 2013

    Apache Rave User Information Disclosure

    Open source ↗

Frequently asked(4)

What is CVE-2013-1814?
CVE-2013-1814 is a none vulnerability published on March 14, 2013. The users/get program in the User RPC API in Apache Rave 0.11 through 0.20 allows remote authenticated users to obtain sensitive information about all user accounts via the offset parameter, as demonstrated by discovering password hashes in the password field of a response.
When was CVE-2013-1814 disclosed?
CVE-2013-1814 was first published in the National Vulnerability Database on March 14, 2013, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2013-1814 actively exploited?
CVE-2013-1814 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2013-1814?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2013-1814, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2013-1814

Explore →

Is Your Infrastructure Affected by CVE-2013-1814?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs