# CVE-2013-2165: Remote code execution due to insecure deserialization > Remote attackers can execute arbitrary code via crafted serialized data due to unrestricted deserialization in the RichFaces library. - **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 22 Jul 2013 - **Updated:** 6 Aug 2024 - **Also known as:** GHSA-4344-frcp-j22q, RHSA-2013:1042, RHSA-2013:1043, RHSA-2013:1044 ## What is CVE-2013-2165? CVE-2013-2165 is a high-severity unsafe deserialization vulnerability in Redhat Jboss Enterprise Application Platform, published on 22 Jul 2013. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-264 ## Which versions are affected by CVE-2013-2165? 4 open source packages ship an affected version, including org.richfaces:richfaces. It affects 8 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.richfaces:richfaces` | Maven | From 3.1.0 | 3.3.3 | | `org.richfaces:richfaces` | Maven | From 3.1.0 | 3.3.3 | | `org.richfaces:richfaces` | Maven | From 4.0.0 | 4.3.2 | | `org.richfaces:richfaces` | Maven | From 4.0.0 | 4.3.2 | | `jboss-seam2` | Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | All versions | 0:2.0.2.FP_SEC1-1.ep2.6.el4 | | `jboss-seam2-docs` | Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | All versions | 0:2.0.2.FP_SEC1-1.ep2.6.el4 | | `jboss-seam2` | Red Hat:jboss_enterprise_application_platform:4.3.0::el5 | All versions | 0:2.0.2.FP_SEC1-1.ep2.6.el5 | | `jboss-seam2-docs` | Red Hat:jboss_enterprise_application_platform:4.3.0::el5 | All versions | 0:2.0.2.FP_SEC1-1.ep2.6.el5 | | `richfaces` | Red Hat:jboss_enterprise_application_platform:5::el4 | All versions | 0:3.3.1-11.SP3_patch_01.ep5.el4 | | `richfaces-demo` | Red Hat:jboss_enterprise_application_platform:5::el4 | All versions | 0:3.3.1-11.SP3_patch_01.ep5.el4 | | `richfaces-framework` | Red Hat:jboss_enterprise_application_platform:5::el4 | All versions | 0:3.3.1-11.SP3_patch_01.ep5.el4 | | `richfaces-root` | Red Hat:jboss_enterprise_application_platform:5::el4 | All versions | 0:3.3.1-11.SP3_patch_01.ep5.el4 | | `richfaces-ui` | Red Hat:jboss_enterprise_application_platform:5::el4 | All versions | 0:3.3.1-11.SP3_patch_01.ep5.el4 | | `richfaces` | Red Hat:jboss_enterprise_application_platform:5::el5 | All versions | 0:3.3.1-6.SP3_patch_01.ep5.el5 | | `richfaces-demo` | Red Hat:jboss_enterprise_application_platform:5::el5 | All versions | 0:3.3.1-6.SP3_patch_01.ep5.el5 | | `richfaces-framework` | Red Hat:jboss_enterprise_application_platform:5::el5 | All versions | 0:3.3.1-6.SP3_patch_01.ep5.el5 | | `richfaces-root` | Red Hat:jboss_enterprise_application_platform:5::el5 | All versions | 0:3.3.1-6.SP3_patch_01.ep5.el5 | | `richfaces-ui` | Red Hat:jboss_enterprise_application_platform:5::el5 | All versions | 0:3.3.1-6.SP3_patch_01.ep5.el5 | | `richfaces` | Red Hat:jboss_enterprise_application_platform:5::el6 | All versions | 0:3.3.1-3.SP3_patch_01.ep5.el6 | | `richfaces-demo` | Red Hat:jboss_enterprise_application_platform:5::el6 | All versions | 0:3.3.1-3.SP3_patch_01.ep5.el6 | | `richfaces-framework` | Red Hat:jboss_enterprise_application_platform:5::el6 | All versions | 0:3.3.1-3.SP3_patch_01.ep5.el6 | | `richfaces-root` | Red Hat:jboss_enterprise_application_platform:5::el6 | All versions | 0:3.3.1-3.SP3_patch_01.ep5.el6 | | `richfaces-ui` | Red Hat:jboss_enterprise_application_platform:5::el6 | All versions | 0:3.3.1-3.SP3_patch_01.ep5.el6 | | `richfaces` | Red Hat:jboss_enterprise_web_platform:5::el5 | All versions | 0:3.3.1-6.SP3_patch_01.ep5.el5 | | `richfaces-demo` | Red Hat:jboss_enterprise_web_platform:5::el5 | All versions | 0:3.3.1-6.SP3_patch_01.ep5.el5 | | `richfaces-framework` | Red Hat:jboss_enterprise_web_platform:5::el5 | All versions | 0:3.3.1-6.SP3_patch_01.ep5.el5 | | `richfaces-root` | Red Hat:jboss_enterprise_web_platform:5::el5 | All versions | 0:3.3.1-6.SP3_patch_01.ep5.el5 | | `richfaces-ui` | Red Hat:jboss_enterprise_web_platform:5::el5 | All versions | 0:3.3.1-6.SP3_patch_01.ep5.el5 | | `richfaces` | Red Hat:jboss_enterprise_web_platform:5::el6 | All versions | 0:3.3.1-3.SP3_patch_01.ep5.el6 | | `richfaces-demo` | Red Hat:jboss_enterprise_web_platform:5::el6 | All versions | 0:3.3.1-3.SP3_patch_01.ep5.el6 | | `richfaces-framework` | Red Hat:jboss_enterprise_web_platform:5::el6 | All versions | 0:3.3.1-3.SP3_patch_01.ep5.el6 | | `richfaces-root` | Red Hat:jboss_enterprise_web_platform:5::el6 | All versions | 0:3.3.1-3.SP3_patch_01.ep5.el6 | | `richfaces-ui` | Red Hat:jboss_enterprise_web_platform:5::el6 | All versions | 0:3.3.1-3.SP3_patch_01.ep5.el6 | Products: Redhat Jboss Enterprise Application Platform, Redhat Jboss Enterprise Brms Platform, Redhat Jboss Enterprise Portal Platform, Redhat Jboss Enterprise Soa Platform, Redhat Jboss Enterprise Web Platform, Redhat Jboss Operations Network, Redhat Jboss Web Framework Kit, Redhat Richfaces. ## How do I fix CVE-2013-2165? Upgrade org.richfaces:richfaces to a fixed version for your release line: 3.3.3 or 4.3.2. ## Is CVE-2013-2165 being exploited? There is no known exploitation of CVE-2013-2165 in the wild and no public exploit code. Public exploit code: - https://github.com/Pastea/CVE-2013-2165 (github_poc): https://github.com/Pastea/CVE-2013-2165 ## Other vulnerabilities in Redhat Jboss Enterprise Application Platform - [CVE-2017-12149](https://insights.sbomify.com/CVE-2017-12149/): Red Hat JBoss Application Server Remote Code Execution (critical 9.8, exploited in the wild) - [CVE-2010-1428](https://insights.sbomify.com/CVE-2010-1428/): Red Hat JBoss Information Disclosure (medium 5.9, exploited in the wild) - [CVE-2010-0738](https://insights.sbomify.com/CVE-2010-0738/): Red Hat JBoss Authentication Bypass (low 3.7, exploited in the wild) - [CVE-2016-3690](https://insights.sbomify.com/CVE-2016-3690/): Deserialization in n/a (critical 9.8) - [CVE-2017-7504](https://insights.sbomify.com/CVE-2017-7504/): Deserialization in JBoss (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2013-2165 and fix it if it is affected. What it is: CVE-2013-2165 is a high-severity unsafe deserialization vulnerability in Redhat Jboss Enterprise Application Platform, published on 22 Jul 2013. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2013-2165 in the wild and no public exploit code. Affected packages and fixed versions: - org.richfaces:richfaces (Maven): affected from 3.1.0; fixed in 3.3.3 - org.richfaces:richfaces (Maven): affected from 3.1.0; fixed in 3.3.3 - org.richfaces:richfaces (Maven): affected from 4.0.0; fixed in 4.3.2 - org.richfaces:richfaces (Maven): affected from 4.0.0; fixed in 4.3.2 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2013-2165/ (Markdown: https://insights.sbomify.com/CVE-2013-2165/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2013-2165 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-2165 - OSV: https://osv.dev/vulnerability/CVE-2013-2165 --- From sbomify Insights: https://insights.sbomify.com/CVE-2013-2165/ Summaries are generated and may contain mistakes; the official description above is the record.