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)?

Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

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 Nov 4, 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

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

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

ResourceBuilderImpl.java in the RichFaces 3.x through 5.x implementation in Red Hat JBoss Web Framework Kit before 2.3.0, Red Hat JBoss Web Platform through 5.2.0, Red Hat JBoss Enterprise Application Platform through 4.3.0 CP10 and 5.x through 5.2.0, Red Hat JBoss BRMS through 5.3.1, Red Hat JBoss SOA Platform through 4.3.0 CP05 and 5.x through 5.3.1, Red Hat JBoss Portal through 4.3 CP07 and 5.x through 5.2.2, and Red Hat JBoss Operations Network through 2.4.2 and 3.x through 3.1.2 does not restrict the classes for which deserialization methods can be called, which allows remote attackers to execute arbitrary code via crafted serialized data.

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`

Affected Products

8 products · 99 configurations

Application

jboss enterprise application platformredhat

7 versions

4.3.05.0.05.0.15.1.05.1.15.1.25.2.0

Application

jboss enterprise brms platformredhat

7 versions

5.0.05.0.15.0.25.1.05.2.05.3.05.3.1

Application

jboss enterprise portal platformredhat

8 versions

4.3.05.0.05.0.15.1.05.1.15.2.05.2.15.2.2

Application

jboss enterprise soa platformredhat

10 versions

4.2.04.3.05.0.05.0.15.0.25.1.05.1.15.2.05.3.05.3.1

Application

jboss enterprise web platformredhat

4 versions

5.1.05.1.15.1.25.2.0

Application

jboss operations networkredhat

15 versions

1.0.02.0.02.0.12.1.02.22.32.3.12.42.4.12.4.23.03.0.1

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
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

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

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.

O3 Security · Impact-Aware SCA

Is CVE-2013-2165 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2013-2165 — richfaces

EPSS Exploitation Probability

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2013-2165 in your dependencies?