What is CVE-2016-4464?

CVE-2016-4464 is a high-severity security vulnerability in org.apache.cxf.fediz:fediz-spring (maven), affecting versions >= 1.2.0, < 1.2.3. It is fixed in 1.2.3, 1.3.1.

Which packages are affected by CVE-2016-4464?

org.apache.cxf.fediz:fediz-spring (maven) versions >= 1.2.0, = 1.2.0, < 1.2.3.

Is there a fix for CVE-2016-4464?

Yes. CVE-2016-4464 is fixed in 1.2.3, 1.3.1. Upgrade to this version or later.

Is CVE-2016-4464 exploitable, and should I be worried?

Whether CVE-2016-4464 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2016-4464 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2016-4464 in org.apache.cxf.fediz:fediz-spring

Q: Which packages are affected by CVE-2016-4464?

org.apache.cxf.fediz:fediz-spring (maven) versions >= 1.2.0, = 1.2.0, < 1.2.3.

Q: Is there a fix for CVE-2016-4464?

Yes. CVE-2016-4464 is fixed in 1.2.3, 1.3.1. Upgrade to this version or later.

Q: Is CVE-2016-4464 exploitable, and should I be worried?

Whether CVE-2016-4464 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2016-4464 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2016-4464?

Upgrade: org.apache.cxf.fediz:fediz-spring to 1.2.3 or later, org.apache.cxf.fediz:fediz-spring to 1.3.1 or later, org.apache.cxf.fediz:fediz-spring2 to 1.2.3 or later, org.apache.cxf.fediz:fediz-spring2 to 1.3.1 or later.

Summary

High severity vulnerability that affects org.apache.cxf.fediz:fediz-spring and org.apache.cxf.fediz:fediz-spring2

The application plugins in Apache CXF Fediz 1.2.x before 1.2.3 and 1.3.x before 1.3.1 do not match SAML AudienceRestriction values against configured audience URIs, which might allow remote attackers to have bypass intended restrictions and have unspecified other impact via a crafted SAML token with a trusted signature.

Impact

Affected versions

org.apache.cxf.fediz:fediz-spring (>= 1.2.0, < 1.2.3) org.apache.cxf.fediz:fediz-spring (= 1.3.0) org.apache.cxf.fediz:fediz-spring2 (>= 1.2.0, < 1.2.3) org.apache.cxf.fediz:fediz-spring2 (= 1.3.0)

Security releases

org.apache.cxf.fediz:fediz-spring → 1.2.3 (maven) org.apache.cxf.fediz:fediz-spring → 1.3.1 (maven) org.apache.cxf.fediz:fediz-spring2 → 1.2.3 (maven) org.apache.cxf.fediz:fediz-spring2 → 1.3.1 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.apache.cxf.fediz:fediz-spring to 1.2.3 or later; org.apache.cxf.fediz:fediz-spring to 1.3.1 or later; org.apache.cxf.fediz:fediz-spring2 to 1.2.3 or later; org.apache.cxf.fediz:fediz-spring2 to 1.3.1 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2016-4464? CVE-2016-4464 is a high-severity security vulnerability in org.apache.cxf.fediz:fediz-spring (maven), affecting versions >= 1.2.0, < 1.2.3. It is fixed in 1.2.3, 1.3.1.
Which packages are affected by CVE-2016-4464?
- org.apache.cxf.fediz:fediz-spring (maven) (versions >= 1.2.0, < 1.2.3)
- org.apache.cxf.fediz:fediz-spring2 (maven) (versions >= 1.2.0, < 1.2.3)
Is there a fix for CVE-2016-4464? Yes. CVE-2016-4464 is fixed in 1.2.3, 1.3.1. Upgrade to this version or later.
Is CVE-2016-4464 exploitable, and should I be worried? Whether CVE-2016-4464 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2016-4464 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2016-4464?
- Upgrade org.apache.cxf.fediz:fediz-spring to 1.2.3 or later
- Upgrade org.apache.cxf.fediz:fediz-spring to 1.3.1 or later
- Upgrade org.apache.cxf.fediz:fediz-spring2 to 1.2.3 or later
- Upgrade org.apache.cxf.fediz:fediz-spring2 to 1.3.1 or later

Other vulnerabilities in org.apache.cxf.fediz:fediz-spring

CVE-IDSeverityPackage summary

CVE-2017-12631Mediumorg.apache.cxf.fediz:fediz-spring2: Moderate severity vulnerability that affects org.apache.cxf.fediz:fediz-spring, org.apache.cxf.fediz:fediz-spring2, and…CVE-2018-8038Highorg.apache.cxf.fediz:fediz-spring: High severity vulnerability that affects org.apache.cxf.fediz:fediz-jetty8, org.apache.cxf.fediz:fediz-jetty9,…