JDK-7166487 : checkSequenceNumber method never called within readRecord of SSLEngineImpl
- Type: Bug
- Component: security-libs
- Sub-Component: javax.net.ssl
- Affected Version: 7
- Priority: P4
- Status: Closed
- Resolution: Fixed
- OS: windows_xp
- CPU: x86
- Submitted: 2012-05-04
- Updated: 2013-08-27
- Resolved: 2012-06-27
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.
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 8 |
|---|
8 b45Fixed  |
Related Reports
|
Relates :
|
Description
FULL PRODUCT VERSION : 1.7.0_01-b08 A DESCRIPTION OF THE PROBLEM : In readRecord method of SSLEngineImpl class, there is o possible way to call checkSequenceNumber method, because handshakeStatus local variable is not assign to NOT_HANDSHAKING anywhere. Same problem occurs in writeRecord method. STEPS TO FOLLOW TO REPRODUCE THE PROBLEM : huge sequence number REPRODUCIBILITY : This bug can be reproduced always.
Comments
|