Summary
Private key leak in Apache CXF
Apache CXF ships with a OpenId Connect JWK Keys service, which allows a client to obtain the public keys in JWK format, which can then be used to verify the signature of tokens issued by the service. Typically, the service obtains the public key from a local keystore (JKS/PKCS12) by specifing the path of the keystore and the alias of the keystore entry. This case is not vulnerable. However it is also possible to obtain the keys from a JWK keystore file, by setting the configuration parameter rs.security.keystore.type to jwk. For this case all keys are returned in this file "as is", including all private key and secret key credentials. This is an obvious security risk if the user has configured the signature keystore file with private or secret key credentials. From CXF 3.3.5 and 3.2.12, it is mandatory to specify an alias corresponding to the id of the key in the JWK file, and only this key is returned. In addition, any private key information is omitted by default. oct keys, which contain secret keys, are not returned at all.
Impact
CVE-2019-12423 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.2.12, 3.3.5); upgrading removes the vulnerable code path.
Affected versions
Security releases
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 environmentNew to Kodem? Get a demo →Remediation advice
org.apache.cxf:apache-cxf to 3.2.12 or later; org.apache.cxf:apache-cxf to 3.3.5 or later; org.apache.cxf:cxf to 3.2.12 or later; org.apache.cxf:cxf to 3.3.5 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2019-12423? CVE-2019-12423 is a high-severity security vulnerability in org.apache.cxf:apache-cxf (maven), affecting versions < 3.2.12. It is fixed in 3.2.12, 3.3.5.
- How severe is CVE-2019-12423? CVE-2019-12423 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which packages are affected by CVE-2019-12423?
org.apache.cxf:apache-cxf(maven) (versions < 3.2.12)org.apache.cxf:cxf(maven) (versions < 3.2.12)
- Is there a fix for CVE-2019-12423? Yes. CVE-2019-12423 is fixed in 3.2.12, 3.3.5. Upgrade to this version or later.
- Is CVE-2019-12423 exploitable, and should I be worried? Whether CVE-2019-12423 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-2019-12423 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-2019-12423?
- Upgrade
org.apache.cxf:apache-cxfto 3.2.12 or later - Upgrade
org.apache.cxf:apache-cxfto 3.3.5 or later - Upgrade
org.apache.cxf:cxfto 3.2.12 or later - Upgrade
org.apache.cxf:cxfto 3.3.5 or later
- Upgrade