CoreCVE
Back

HIGH

cxf: OpenId Connect token service does not properly validate the clientId

Published Jan 16, 2020

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 products

Remediation

No remediation recorded yet.

Metrics

Weaknesses (1)

CWE-522

Insufficiently Protected Credentials

References (21)

Change history (0)

No recorded changes yet.

Sources
CVE.org / MITRE
Status PUBLISHED
Assigner apache
Published Jan 16, 2020
Updated Aug 4, 2024
Reserved May 28, 2019
Link CVE-2019-12423
CISA Vulnrichment
Updated n/a
NVD
Status Modified
Modified Jun 17, 2026
Link CVE-2019-12423
Red Hat
Severity Moderate
Public date Jan 16, 2020
Links CVE-2019-12423 - Bugzilla
GHSA-42F2-F9VC-6365