Project

General

Profile

Actions
Copy link

Security #5254

closed

protocol detection: exploitable type confusion due to concurrent protocol changes

Added by Jeff Lucovsky over 2 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Shivani Bhardwaj
Target version:
6.0.6
Affected Versions:
Label:
CVE:
Git IDs:

e55eeb3bdee1a57f17a21ca509385c84caaa4469

Severity:
MODERATE
Disclosure Date:

Description

Found by oss-fuzz
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45941&q=label%3AProj-suricata&can=2

If a STMP session has STARTTLS, it requests AppLayerRequestProtocolChange
We call TCPProtoDetect to rerun protocol detection
So far, so good.

But then, if the protocol is HTTP1 requesting an upgrade, HTTP/1.1 101\nUpgrade:h2c
we call again AppLayerRequestProtocolChange which erases values like alproto_orig which leads to type confusion...

Files

range.pcap (621 Bytes) range.pcap Philippe Antoine, 04/08/2022 12:32 PM

Related issues 1 (0 open — 1 closed)

Copied from Suricata - Security #5243: protocol detection: exploitable type confusion due to concurrent protocol changesClosedPhilippe AntoineActions
Actions
Copy link

Also available in: Atom PDF