How severe is CVE-2011-4314?

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

Which packages are affected by CVE-2011-4314?

CVE-2011-4314 affects the following packages: org.openid4java:openid4java (Maven). Ecosystems affected: Maven.

How do I fix CVE-2011-4314?

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

How do I detect CVE-2011-4314 in my Maven dependencies?

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

How do I mitigate CVE-2011-4314 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-2011-4314?

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

Is CVE-2011-4314 actively exploited in the wild?

No public exploit code has been indexed for CVE-2011-4314 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-2011-4314?

CVE-2011-4314 has an EPSS (Exploit Prediction Scoring System) score of 3.1%, placing it in the 87th 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 indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2011-4314?

CVE-2011-4314 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2011-4314 published, and has it been updated?

CVE-2011-4314 was published on January 27, 2012 and was last updated on April 10, 2026. 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-2011-4314 — openid4java

CVE-2011-4314 is a Improper Input Validation vulnerability in org.openid4java:openid4java. A fix is available for org.openid4java:openid4java — see the affected versions and patch details below.

OpenID4Java does not verify that Attribute Exchange (AX) information is signed

Also known asGHSA-j473-c3rr-rx9p

Published

Jan 27, 2012

Updated

Apr 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

3.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs87th percentile — riskier than 87% 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

1 pkg affected

☕org.openid4java:openid4java

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

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.openid4java:openid4java`	all versions	0.9.6`org.openid4java:openid4java:0.9.6`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.openid4java:openid4java, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.openid4java:openid4java to 0.9.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2011-4314 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-2011-4314 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2011-4314. 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 HatLow

Product	Fixed in	Advisory
JBEWP 5 for RHEL 5	`apache-cxf-0:2.2.12-4.patch_02.1.1.ep5.el5`	RHSA-2011:1803
JBEWP 5 for RHEL 6	`apache-cxf-0:2.2.12-4.patch_02.1.ep5.el6`	RHSA-2011:1802
JBoss Enterprise BRMS Platform 5.2	see advisory	RHSA-2012:0441
Red Hat JBoss Enterprise Application Platform 5.1	see advisory	RHSA-2011:1805
Red Hat JBoss Enterprise Application Platform 5 for RHEL 5	`apache-cxf-0:2.2.12-4.patch_02.1.1.ep5.el5`	RHSA-2011:1799
Red Hat JBoss Enterprise Application Platform 5 for RHEL 6	`apache-cxf-0:2.2.12-4.patch_02.1.ep5.el6`	RHSA-2011:1798
Red Hat JBoss Portal 5.2	see advisory	RHSA-2012:0519
Red Hat JBoss SOA Platform 5.2	see advisory	RHSA-2012:0378

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2011-4314 in your dependencies?

O3 Security finds CVE-2011-4314 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