Actions
Security #955
closedSSL parsing issue
Git IDs:
b7f6f9724595e7f595c3cc4fc9fa4d3d0839e122
8ec28dea16080c77828412d6de01018dabc7b7c3
Severity:
Disclosure Date:
Description
CVE-2013-5919 reported by Sebastian Roschke.
Updated by Victor Julien about 11 years ago
- Status changed from Assigned to Closed
- Private changed from Yes to No
Fixed by:
commit 70c535220ebcfa111cb1878b658b8dbe302b380d Author: Anoop Saldanha <anoopsaldanha@gmail.com> Date: Tue Sep 24 11:31:37 2013 +0530 Add decoder event rule for tls event "invalid_ssl_record", which will now be available "app-layer-event:tls.invalid_ssl_record". commit b7f6f9724595e7f595c3cc4fc9fa4d3d0839e122 Author: Anoop Saldanha <anoopsaldanha@gmail.com> Date: Fri Sep 13 19:57:29 2013 +0530 bug #955 - Fix SSL parsing issue. The parser wasn't carrying out a bounds check on record length while in the middle of parsing a handshake. As a result we would step onto the next record header and consider it a part of the current handshake. - Contains an unittest to test the issue. - Disable the duplicate parser unittest registration. The issue came to light through an irregular ssl record, which was reported by Sebastian Roschke, via CVE-2013-5919. Thanks to Sebastian Roschke for reporting this issue.
Updated by Victor Julien over 4 years ago
- Tracker changed from Bug to Security
- CVE set to 2013-5919
- Git IDs updated (diff)
Actions