CVE-2019-12423
HIGHEPSS 93th pctlDescription
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.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Exploit Intelligence
High risk: more likely to be exploited than 93% of all known CVEs.
References
Related Vulnerabilities
Other CWE-522 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2019-17662 | Critical | 9.8 | 97% | - | - |
| CVE-2020-29583 | Critical | 9.8 | 90% | KEV | - |
| CVE-2021-30116 | Critical | 10.0 | 86% | KEV + Ransom | Fix |
| CVE-2024-44000 | Critical | 9.8 | 82% | - | Fix |
| CVE-2018-9160 | Critical | 9.8 | 76% | - | - |
| CVE-2017-9248 | Critical | 9.8 | 75% | KEV | Fix |
Common questions
How do I fix CVE-2019-12423?
Upgrade cxf to 3.3.5 or later.
Is CVE-2019-12423 being actively exploited?
Not that we know of. CVE-2019-12423 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 6.1% is the estimated probability that it will be exploited in the next 30 days. That is higher than 93% of all scored CVEs.
How severe is CVE-2019-12423?
CVE-2019-12423 has a CVSS v3 base score of 7.5, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2019-12423 affect?
Published advisories record a fix for cxf (NVD). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2019-12423
Markdown
[](https://tridentstack.com/cve/CVE-2019-12423)HTML
<a href="https://tridentstack.com/cve/CVE-2019-12423"><img src="https://tridentstack.com/cve/badge/CVE-2019-12423.svg" alt="CVE-2019-12423"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2024-11-21.