Actions
Bug #6964
closedbase64: consumed bytes are incorrectly set for different modes
Affected Versions:
Effort:
Difficulty:
Label:
Description
For example, given a string 0YPhA d H and an ample buffer size, consumed bytes should be 4 in RFC2045 mode as there are only 3 valid bytes post 0YPh and that isn't enough to decode. Actually, looking further, it seems we want to decode all the bytes that we can as long as there is ample destination space but only for RFC 4648.
Updated by Shivani Bhardwaj over 1 year ago
- Status changed from Assigned to In Review
In Review PR: https://github.com/OISF/suricata/pull/10892
Updated by Shivani Bhardwaj over 1 year ago
- Blocks Task #6050: base64: make a fuzz target added
Updated by Shivani Bhardwaj over 1 year ago
- Status changed from In Review to Closed
Closed by: https://github.com/OISF/suricata/pull/10941
Updated by Philippe Antoine about 1 year ago
- Related to Bug #7028: base64: heap buffer overflow in RFC 2045 and 4648 modes added
Actions