[CXF-8177] JWE API does not support ECDH Direct Encryption/Decryption

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.3.4
• Fix Version/s: 3.3.5, 3.4.0
• Component/s: JAX-RS Security
• Estimated Complexity: Unknown
• Assignee: Colm O hEigeartaigh
• Reporter: Frederik Libert
• Created: 05/Dec/19 10:42
• Updated: 15/Jan/20 10:24
• Resolved: 20/Dec/19 12:52

Description

Although the Apache CXF implementation of JWE supports ECDH Direct encryption/decryption, the API is not sufficiently open for it.

A few problems:

• KeyAlgorithm.getAlgorithm(String) does not support parsing ECDH
• EcdhDirectKeyDecryptionAlgorithm is a private innerclass so cannot be used from the clientview perspective (different approach for different algorithms, why?)
• EcdhDirectKeyJweDecryption makes an assumption that AES GCM is used without verifying (could be AES CBC as well)
• JweUtils.getPrivateKeyDecryptionProvider(PrivateKey,KeyAlgorithm)  makes an assumption that AESWrap is used in case of an EC Key without veryfing the KeyAlgorithm (could be Direct as well)

The API should support proper handling of key algorithm between client and library and should verify what is given as input to decide which key and content decrypters to use.

 

Issue Links

• is related to: CXF-8178 ECDH KeyAgreement with Key Wrapping is not in line with the specification
• is related to: CXF-8185 Generated Ephemeral Public Key missing in JWE Headers when Json Serialization is used
• links to: GitHub Pull Request #612