# CVE-2011-4314: OpenID4Java does not verify that Attribute Exchange (AX) information is signed > Remote attackers can modify sensitive OpenID Attribute Exchange data without detection via man-in-the-middle attacks due to missing signature verification. - **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:N/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:** 27 Jan 2012 - **Updated:** 7 Aug 2024 - **Also known as:** DEBIAN-CVE-2011-4314, GHSA-j473-c3rr-rx9p, RHSA-2011:1802, RHSA-2011:1803, RHSA-2011:1804 ## What is CVE-2011-4314? CVE-2011-4314 is a medium-severity vulnerability in Redhat Jboss Enterprise Application Platform, published on 27 Jan 2012. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description message/ax/AxMessage.java in OpenID4Java before 0.9.6 final, as used in JBoss Enterprise Application Platform 5.1 before 5.1.2, Step2, Kay Framework before 1.0.2, and possibly other products does not verify that Attribute Exchange (AX) information is signed, which allows remote attackers to modify potentially sensitive AX information without detection via a man-in-the-middle (MITM) attack. Weakness: CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2011-4314? 2 open source packages ship an affected version, including org.openid4java:openid4java. It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.openid4java:openid4java` | Maven | All versions | 0.9.6 | | `org.openid4java:openid4java` | Maven | All versions | 0.9.6 | | `apache-cxf` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:2.2.12-4.patch_02.1.1.ep5.el4 | | `cglib` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:2.2-5.3.ep5.el4 | | `facelets` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:1.1.15-3.B1_patch_01.2.ep5.el4 | | `glassfish-jaxb` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:2.1.12-10_patch_02.ep5.el4 | | `glassfish-jsf` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:1.2_13-5_patch_01.3.ep5.el4 | | `jacorb-jboss` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:2.3.1-10.patch_03.4.ep5.el4 | | `jakarta-commons-logging-jboss` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:1.1-10.3_patch_02.1.ep5.el4 | | `jboss-aop2` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:2.1.6-2.CP03.1.1.ep5.el4 | | `jboss-cache-core` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:3.2.8-1.ep5.el4 | | `jboss-cl` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:2.0.10-1.2.ep5.el4 | | `jboss-cluster-ha-client` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:1.1.4-1.1.ep5.el4 | | `jboss-common-core` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:2.2.18-1.1.ep5.el4 | | `jboss-eap5-native` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:5.1.2-1.4.ep5.el4 | | `jboss-ejb3-core` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:1.3.8-0.1.ep5.el4 | | `jboss-ejb3-proxy-clustered` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:1.0.3-2.SP1.1.ep5.el4 | | `jboss-ejb3-proxy-impl` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:1.0.6-2.SP2.1.ep5.el4 | | `jboss-el` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:1.0_02-0.CR6.2.ep5.el4 | | `jboss-naming` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:5.0.3-3.CP01.3.1.ep5.el4 | | `jboss-remoting` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:2.5.4-9.SP3.1.ep5.el4 | | `jboss-seam2` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:2.2.5.EAP5-6.ep5.el4 | | `jboss-seam2-docs` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:2.2.5.EAP5-6.ep5.el4 | | `jboss-seam2-examples` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:2.2.5.EAP5-6.ep5.el4 | | `jboss-seam2-runtime` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:2.2.5.EAP5-6.ep5.el4 | | `jboss-security-spi` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 1:2.0.4-6.SP8.1.ep5.el4 | | `jbossas-web` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:5.1.2-7.ep5.el4 | | `jbossas-web-client` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:5.1.2-7.ep5.el4 | | `jbossas-web-tp-licenses` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:5.1.2-8.ep5.el4 | | `jbossas-web-ws-native` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:5.1.2-7.ep5.el4 | | `jbossas-ws-cxf-ewp` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:5.1.2-6.ep5.el4 | | `jbosssx2` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:2.0.4-6.SP8.2.ep5.el4 | | `jbossts` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 1:4.6.1-11.CP12.4.ep5.el4 | | `jbossts-javadoc` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 1:4.6.1-11.CP12.4.ep5.el4 | | `jbossweb` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:2.1.12-1.4_patch_01.ep5.el4 | | `jbossweb-el-1.0-api` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:2.1.12-1.4_patch_01.ep5.el4 | | `jbossweb-jsp-2.1-api` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:2.1.12-1.4_patch_01.ep5.el4 | | `jbossweb-lib` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:2.1.12-1.4_patch_01.ep5.el4 | | `jbossweb-servlet-2.5-api` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:2.1.12-1.4_patch_01.ep5.el4 | | `jbossws` | Red Hat:jboss_enterprise_web_platform:5::el4 | All versions | 0:3.1.2-7.SP11.4.ep5.el4 | Products: Kay Framework Project Kay Framework, Openid Openid4java, Redhat Jboss Enterprise Application Platform. ## How do I fix CVE-2011-4314? Upgrade org.openid4java:openid4java to 0.9.6 or later. ## Is CVE-2011-4314 being exploited? There is no known exploitation of CVE-2011-4314 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2011-4314 and fix it if it is affected. What it is: CVE-2011-4314 is a medium-severity vulnerability in Redhat Jboss Enterprise Application Platform, published on 27 Jan 2012. 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-2011-4314 in the wild and no public exploit code. Affected packages and fixed versions: - org.openid4java:openid4java (Maven): affected all versions; fixed in 0.9.6 - org.openid4java:openid4java (Maven): affected all versions; fixed in 0.9.6 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-2011-4314/ (Markdown: https://insights.sbomify.com/CVE-2011-4314/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2011-4314 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2011-4314 - OSV: https://osv.dev/vulnerability/CVE-2011-4314 --- From sbomify Insights: https://insights.sbomify.com/CVE-2011-4314/ Summaries are generated and may contain mistakes; the official description above is the record.