JDK-8224240 : Properties.load fails to throw IAE on malformed unicode in certain circumstances
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util
  • Affected Version: 5.0,6,7,8,11,12,13
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2019-05-20
  • Updated: 2019-06-27
  • Resolved: 2019-06-05
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 13
13 b24Fixed
Related Reports
CSR :  
Sub Tasks
JDK-8226735 :  
Description
A property file like the following should fail to load with an IAE

a=\u0

but if there's a preceding property like this, it might mis-parse instead:

b=\u0123
a=\u0

-> property a erroneously becomes \u0123

Fixing this might mean some properties files that were malformed would go from being silently misparsed to throwing an IllegalArgumentException, so a CSR will be filed.