How severe is CVE-2013-2165?

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

Which packages are affected by CVE-2013-2165?

CVE-2013-2165 affects the following packages: org.richfaces:richfaces (Maven), org.richfaces:richfaces (Maven). Ecosystems affected: Maven.

How do I fix CVE-2013-2165?

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

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

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

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2013-2165?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2013-2165 can be triaged on real exposure rather than presence alone.

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

No public exploit code has been indexed for CVE-2013-2165 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

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

CVE-2013-2165 has an EPSS (Exploit Prediction Scoring System) score of 12.7%, placing it in the 96th 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. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2013-2165?

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

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

CVE-2013-2165 was published on May 13, 2022 and was last updated on November 8, 2023. 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-2165 — richfaces

CVE-2013-2165 is a CWE-264 vulnerability in org.richfaces:richfaces. EPSS puts its 30-day exploitation probability at 12.7% (96th percentile). A fix is available for org.richfaces:richfaces — see the affected versions and patch details below.

Remote code execution due to insecure deserialization

Published

May 13, 2022

Updated

Nov 8, 2023

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

12.7%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs96th percentile — riskier than 96% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

2 pkgs affected

☕org.richfaces:richfaces☕org.richfaces:richfaces

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

A flaw was found in the way JBoss RichFaces handled deserialization. A remote attacker could use this flaw to trigger the execution of the deserialization methods in any serializable class deployed on the server. This could lead to a variety of security impacts depending on the deserialization logic of these classes.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.richfaces:richfaces`	≥ 3.1.0&&< 3.3.3	3.3.3`org.richfaces:richfaces:3.3.3`
☕Maven	`org.richfaces:richfaces`	≥ 4.0.0&&< 4.3.2	4.3.2`org.richfaces:richfaces:4.3.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.richfaces:richfaces, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.richfaces:richfaces to 3.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-2165 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2013-2165 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2013-2165. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatCritical

Product	Fixed in	Advisory
JBEWP 5 for RHEL 5	`richfaces-0:3.3.1-6.SP3_patch_01.ep5.el5`	RHSA-2013:1043
JBoss Enterprise BRMS Platform 5.3	see advisory	RHSA-2013:1045
Red Hat JBoss Enterprise Application Platform 4.3 for RHEL 4	`jboss-seam2-0:2.0.2.FP_SEC1-1.ep2.6.el4`	RHSA-2013:1044
Red Hat JBoss Enterprise Application Platform 5 for RHEL 4	`richfaces-0:3.3.1-11.SP3_patch_01.ep5.el4`	RHSA-2013:1042
Red Hat JBoss Web Framework Kit 2.3	see advisory	RHSA-2013:1041

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2013-2165 in your dependencies?

O3 Security finds CVE-2013-2165 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works