Project

General

Profile

Actions

Bug #6964

closed

base64: consumed bytes are incorrectly set for different modes

Added by Shivani Bhardwaj 14 days ago. Updated 7 days ago.

Status:
Closed
Priority:
Normal
Target version:
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.


Related issues 1 (1 open0 closed)

Blocks Suricata - Task #6050: base64: make a fuzz targetIn ReviewShivani BhardwajActions
Actions #1

Updated by Shivani Bhardwaj 14 days ago

  • Description updated (diff)
Actions #2

Updated by Shivani Bhardwaj 14 days ago

  • Description updated (diff)
Actions #3

Updated by Shivani Bhardwaj 14 days ago

  • Status changed from Assigned to In Review
Actions #4

Updated by Shivani Bhardwaj 14 days ago

  • Blocks Task #6050: base64: make a fuzz target added
Actions #5

Updated by Shivani Bhardwaj 7 days ago

  • Status changed from In Review to Closed
Actions

Also available in: Atom PDF