CVE-2019-12423 — apache-cxf
HIGHCVE-2019-12423 is a high-severity (CVSS 7.5) CWE-522 vulnerability in org.apache.cxf:apache-cxf. 4 public exploit references exist, so weaponization risk is real. A fix is available for org.apache.cxf:apache-cxf — see the affected versions and patch details below.
Private key leak in Apache CXF
EPSS Exploitation Probability
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.
How urgent is this, really
CVE-2019-12423 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.apache.cxf:apache-cxf☕org.apache.cxf:apache-cxf☕org.apache.cxf:cxf☕org.apache.cxf:cxfReal-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
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.cxf:apache-cxf | all versions | 3.2.12org.apache.cxf:apache-cxf:3.2.12 |
| ☕Maven | org.apache.cxf:apache-cxf | ≥ 3.3.0&&< 3.3.5 | 3.3.5org.apache.cxf:apache-cxf:3.3.5 |
| ☕Maven | org.apache.cxf:cxf | all versions | 3.2.12org.apache.cxf:cxf:3.2.12 |
| ☕Maven | org.apache.cxf:cxf | ≥ 3.3.0&&< 3.3.5 | 3.3.5org.apache.cxf:cxf:3.3.5 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Apache CXF ships with a OpenId Connect JWK Keys service, which allows a …
Apache CXF ships with a OpenId Connect JWK Keys service, which allows a …
Apache CXF ships with a OpenId Connect JWK Keys service, which allows a …
Apache CXF ships with a OpenId Connect JWK Keys service, which allows a …
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.cxf:apache-cxf, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.cxf:apache-cxf to 3.2.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-12423 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-2019-12423 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2019-12423. 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.
| Product | Fixed in | Advisory |
|---|---|---|
| EAP-CD 19 Tech Preview | cxf-core | RHSA-2020:2333 |
| Red Hat Decision Manager 7 | cxf-core | RHSA-2020:3196 |
| Red Hat Fuse 7.8.0 | cxf-core | RHSA-2020:5568 |
| Red Hat JBoss EAP 7 | cxf-core | RHSA-2020:2515 |
| Red Hat JBoss EAP 7.2 | cxf-core | RHSA-2020:2061 |
| Red Hat JBoss Enterprise Application Platform 7.2 for RHEL 6 | eap7-activemq-artemis-0:2.9.0-4.redhat_00010.1.el6eap | RHSA-2020:2058 |
| Red Hat JBoss Enterprise Application Platform 7.2 for RHEL 7 | eap7-activemq-artemis-0:2.9.0-4.redhat_00010.1.el7eap | RHSA-2020:2059 |
| Red Hat JBoss Enterprise Application Platform 7.2 for RHEL 8 | eap7-activemq-artemis-0:2.9.0-4.redhat_00010.1.el8eap | RHSA-2020:2060 |
Frequently Asked Questions
Is CVE-2019-12423 in your dependencies?
O3 Security finds CVE-2019-12423 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.