#27460 [Opn->Csd]: base64_decode fails to follow RFC 3548 completely
| From: | iliaa@php.net | Date: | Sat, 06 Mar 2004 18:58:10 +0000 |
| Subject: | #27460 [Opn->Csd]: base64_decode fails to follow RFC 3548 completely | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-56001@lists.php.net to get a copy of this message | ||
ID: 27460
Updated by: iliaa@php.net
Reported By: naish at klanen dot net
-Status: Open
+Status: Closed
Bug Type: URL related
Operating System: Suse Linux 9.0 (2.4.21)
PHP Version: 4.3.4
New Comment:
This bug has been fixed in CVS.
Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at
http://snaps.php.net/.
Thank you for the report, and for helping us make PHP better.
Previous Comments:
------------------------------------------------------------------------
[2004-03-02 09:43:21] naish at klanen dot net
Description:
------------
If a base64 encoded string contains a non-needed "=" at the end of the
string base64_decode returns false even though the string has been
correctly decoded.
The standard for base64 even specifies that a file may contain
non-needed padding chars.
http://www.faqs.org/rfcs/rfc3548.html
- snip -
Furthermore, such specifications may consider the pad character, "=",
as not part of the base alphabet until the end of the string. If more
than the allowed number of pad characters are found at the end of the
string, e.g., a base 64 string terminated with "===", the excess pad
characters could be ignored.
- /snip -
The fix is simple. In ext/standard/base64.c insert the following code:
if (ch == base64_pad) {
switch(i % 4) {
case 1:
efree(result);
return NULL;
case 2:
k++;
case 3:
result[k++] = 0;
}
}
in the base64_decode function. Notice that the only thing I did was
remove "case 0:" on line 191.
Reproduce code:
---------------
<?php
$string=base64_encode("123456");
echo $string."\n";
//Insert a not-needed padding char.
$string.="=";
//This returns false even though $string is valid base64
var_dump(base64_decode($string));
?>
Expected result:
----------------
$string should been encoded to base64 and later decoded with 1 extra
"=" added at the end.
Actual result:
--------------
PHP fails to decode the string properly.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=27460&edit=1