CVE-2019-12423

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.

• apache cxf (< 3.2.12) • apache cxf (>= 3.3.0 < 3.3.5) • oracle commerce guided search 11.3.2 • oracle communications diameter signaling router (>= 8.0.0 <= 8.2.2) • oracle communications element manager (>= 8.2.0 <= 8.2.2) • oracle communications session report manager (>= 8.2.0 <= 8.2.2) • oracle communications session route manager 8.1.1 • oracle communications session route manager 8.2.0 • oracle communications session route manager 8.2.1 • oracle flexcube private banking 12.0.0 • oracle flexcube private banking 12.1.0 • oracle retail order broker 15.0