Skip to content
Fencer Intel
medium 4.0

CVE-2013-1814 json

Apache Rave information disclosure vulnerability

published 13y ago modified 4mo ago also GHSA-428j-q447-47rw , EUVD-2022-2267

cvss
4.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
73.6%
EPSS 73.6% chance of exploitation in 30 days, percentile 99.4%
public exploits
2
Metasploit and Exploit-DB

Summary

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.

Patch / fix

  • maven org.apache.rave:rave-core 0.20.1
  • maven org.apache.rave:rave-web 0.20.1
  • maven org.apache.rave:rave-portal-resources 0.20.1

Is CVE-2013-1814 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (EDB-24744)
  2. Published

Exploit prediction

73.64% chance of exploitation in the next 30 days, higher than 99.4% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

CVSS scores

assigned by version score vector
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.apache.rave:rave-core
>=0.11, <0.20.1
0.20.1
maven org.apache.rave:rave-web
>=0.11, <0.20.1
0.20.1
maven org.apache.rave:rave-portal-resources
>=0.11, <0.20.1
0.20.1

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

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.