JDK-8223003 : SunMSCAPI keys are not cleaned up
  • Type: Bug
  • Component: security-libs
  • Sub-Component: javax.crypto
  • Affected Version: 12
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2019-04-26
  • Updated: 2020-06-09
  • Resolved: 2019-04-29
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 11 JDK 12 JDK 13 JDK 8 Other
11.0.7-oracleFixed 12.0.2Fixed 13 b19Fixed 8u251Fixed openjdk8u252Fixed
Related Reports
Relates :  
JDK-8026953 - Add support for MS Cryptography next generation (CNG)
Relates :  
JDK-8163896 - Finalizing one key of a KeyPair invalidates the other key
Description
The native CKey::cleanup method is not implemented. We also need to make sure the handles are only released when both the private key and the public key (which share the same handles) are not referenced anymore.
Comments
Fix request (11u) I would like to downport this for parity with 11.0.7-oracle. Applies clean.
03-01-2020
Fix request (for JDK 12u) This fixes two regressions in JDK 12: one resulted in a leak of resources (native handles of crypto objects were not properly released), and the other was the issue previously fixed via JDK-8163896. Source patch from JDK 13 applies cleanly.
27-04-2019