Bugtraq mailing list archives
RE: base64
From: <latte () hushmail com>
Date: Mon, 22 Sep 2003 17:52:25 -0700
What about this section: " Because it is used only for padding at the end of the data, the occurrence of any '=' characters may be taken as evidence that the end of the data has been reached (without truncation in transit). No such assurance is possible, however, when the number of octets transmitted was a multiple of three. " From: http://www.ietf.org/rfc/rfc1521.txt?number=1521 Seems to suggest that it should be treated as the end of input. -----Original Message----- From: "Ilya Teterin" [mailto:alienhard () mail ru] Sent: Monday, 22 September 2003 10:50 PM To: bugtraq () securityfocus com Subject: base64 Consider we decoding data which contains padding character ('=') at the unexpected place. What we should do with such data? The specification of base64 decoding does not tell us what we MUST or even MAY do with such data... So, we can do anything we like to do: 1. threat padding character as end of the encoded data 2. ignore padding character 3. decode padding character as well as some other character from base64 alphabet 4. do something else ;-) I have tested some popular implementations (such as email clients, GNU utilities, RTL and other development's libraries). All items (1)-(4) are actually present. Is it dangerous? Sure. Consider antiviral software, which implements behaviour (1), and e-mail client, which implements behaviour (2). Attacker can insert padding character in the beginning of the encoded data, and antiviral software will think encoded data is empty. But e-mail client will think differentother way ;-) So, bypassing of content-filtering and antiviral protection is obvious subject for this issue. How to solve this issue? I believe we should rewrite at least filtering systems to block malformed base64-encoded data because we don't know is it malicious or not. Otherwise, we can meet new powerful e-mail worm. ----- "Will research information security for food!" Concerned about your privacy? Follow this link to get FREE encrypted email: https://www.hushmail.com/?l=2 Free, ultra-private instant messaging with Hush Messenger https://www.hushmail.com/services.php?subloc=messenger&l=434 Promote security and make money with the Hushmail Affiliate Program: https://www.hushmail.com/about.php?subloc=affiliate&l=427
Current thread:
- Re: base64, (continued)
- Re: base64 Lothar Kimmeringer (Sep 24)
- Re: base64 David Wilson (Sep 24)
- Re: base64 Earl Hood (Sep 25)
- Re: base64 Christian Vogel (Sep 25)
- Re: base64 Seth Breidbart (Sep 24)
- Re: base64 Lothar Kimmeringer (Sep 24)
- Re: base64 Alexander Ogol (Sep 23)
- Re: base64 Christian Vogel (Sep 24)
- Re: base64 David Wilson (Sep 24)
- Re: base64 der Mouse (Sep 24)
- Re: base64 Christian Vogel (Sep 24)
- Re: base64 Earl Hood (Sep 26)
- RE: base64 latte (Sep 23)
- Re: base64 Ilya Teterin (Sep 23)
- Re: base64 MightyE (Sep 24)
- Re: base64 Buck Huppmann (Sep 24)
- Re: base64 Andrew Church (Sep 25)
- Message not available
- Re: base64 MightyE (Sep 25)
- Re: base64 Bennett Todd (Sep 25)
- Re: base64 MightyE (Sep 25)
- Re: base64 Earl Hood (Sep 26)
- Re: base64 Bennett Todd (Sep 26)
- Re[2]: base64 3APA3A (Sep 26)
- Re: base64 Buck Huppmann (Sep 24)