How severe is CVE-2013-1814?

No CVSS score has been assigned to CVE-2013-1814 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2013-1814?

CVE-2013-1814 affects the following packages: org.apache.rave:rave-core (Maven), org.apache.rave:rave-web (Maven), org.apache.rave:rave-portal-resources (Maven). Ecosystems affected: Maven.

How do I fix CVE-2013-1814?

Update org.apache.rave:rave-core to 0.20.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-1814 is resolved across your whole dependency graph.

How do I detect CVE-2013-1814 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.rave:rave-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2013-1814 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2013-1814 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2013-1814, including 1 documented proof-of-concept exploit on Exploit-DB and 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2013-1814?

CVE-2013-1814 has an EPSS (Exploit Prediction Scoring System) score of 73.6%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2013-1814?

CVE-2013-1814 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2013-1814 published, and has it been updated?

CVE-2013-1814 was published on May 17, 2022 and was last updated on December 6, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2013-1814 — rave-core

Fix: apache/rave@546edba

CVE-2013-1814 is a Information Exposure vulnerability in org.apache.rave:rave-core. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.apache.rave:rave-core — see the affected versions and patch details below.

Apache Rave information disclosure vulnerability

Published

May 17, 2022

Updated

Dec 6, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

3 known

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

73.6%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected

☕org.apache.rave:rave-core☕org.apache.rave:rave-web☕org.apache.rave:rave-portal-resources

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.rave:rave-core`	≥ 0.11&&< 0.20.1	0.20.1`org.apache.rave:rave-core:0.20.1`
☕Maven	`org.apache.rave:rave-web`	≥ 0.11&&< 0.20.1	0.20.1`org.apache.rave:rave-web:0.20.1`
☕Maven	`org.apache.rave:rave-portal-resources`	≥ 0.11&&< 0.20.1	0.20.1`org.apache.rave:rave-portal-resources:0.20.1`

Affected Products

1 product · 10 configurations

Application

raveapache

10 versions

0.110.120.130.140.150.160.170.180.190.20

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-24744webappsmultiple

Apache Rave 0.11 < 0.20 - User Information Disclosure

by Andreas Guth · Mar 13, 2013

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.rave:rave-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.rave:rave-core to 0.20.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-1814 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2013-1814 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works