Secunia
|
|

|
|
|
|
|
|
|
Release Date: 2010-05-04 Last Update: 2010-08-26 Views: 5,398
Where:
From remote
Impact:
Exposure of sensitive information, DoS, System access,
Solution Status:
Partial Fix
CVE Reference(s):
Stefan Esser has reported some vulnerabilities in PHP, which can be exploited by malicious people to disclose potentially sensitive information, cause a DoS (Denial of Service), or potentially compromise a vulnerable system.
1) The implementation of the "addcslashes()" function is not properly protected against function interruptions, which can be exploited to disclose potentially sensitive information.
2) The implementation of the "chunk_split()" function is not properly protected against function interruptions, which can be exploited to disclose potentially sensitive information.
3) The implementation of the "html_entity_decode()" function is not properly protected against function interruptions, which can be exploited to disclose potentially sensitive information.
4) The implementation of the "iconv_mime_decode()" function is not properly protected against function interruptions, which can be exploited to disclose potentially sensitive information.
5) The implementation of the "iconv_substr()" function is not properly protected against function interruptions, which can be exploited to disclose potentially sensitive information.
6) The implementation of the "iconv_mime_encode()" function is not properly protected against function interruptions, which can be exploited to disclose potentially sensitive information.
7) The implementation of the "htmlentities()" and "htmlspecialchars()" functions is not properly protected against function interruptions, which can be exploited to disclose potentially sensitive information.
8) The implementation of the "str_getcsv()" function is not properly protected against function interruptions, which can be exploited to disclose potentially sensitive information.
9) The implementation of the "http_build_query()" function is not properly protected against function interruptions, which can be exploited to disclose potentially sensitive information.
10) The implementation of the "strpbrk()" function is not properly protected against function interruptions, which can be exploited to disclose potentially sensitive information.
11) The implementation of the "strtr()" function is not properly protected against function interruptions, which can be exploited to disclose potentially sensitive information.
12) The implementation of the "str_pad()" function is not properly protected against function interruptions, which can be exploited to disclose potentially sensitive information.
13) The implementation of the "str_word_count()" function is not properly protected against function interruptions, which can be exploited to disclose potentially sensitive information.
14) The implementation of the "wordwrap()" function is not properly protected against function interruptions, which can be exploited to disclose potentially sensitive information.
15) The implementation of the "strtok()" function is not properly protected against function interruptions, which can be exploited to disclose potentially sensitive information.
16) The implementation of the "setcookie()" function is not properly protected against function interruptions, which can be exploited to disclose potentially sensitive information.
17) The implementation of the "strip_tags()" function is not properly protected against function interruptions, which can be exploited to disclose potentially sensitive information.
18) The implementation of the "trim()", "ltrim()", and "rtrim()" functions is not properly protected against function interruptions, which can be exploited to disclose potentially sensitive information.
19) The implementation of the "substr_replace()" function is not properly protected against function interruptions, which can be exploited to disclose potentially sensitive information.
20) The implementation of the "parse_str()" function is not properly protected against function interruptions, which can be exploited to disclose potentially sensitive information.
21) The implementation of the ZEND_CONCAT and ZEND_ASSIGN_CONCAT opcodes is not properly protected against function interruptions, which can be exploited to disclose potentially sensitive information, or corrupt memory and cause a crash.
22) The implementation of the "pack()" function is not properly protected against function interruptions, which can be exploited to disclose potentially sensitive information.
23) The implementation of the "unpack()" function is not properly protected against function interruptions, which can be exploited to disclose potentially sensitive information.
24) The implementation of the ZEND_FETCH_RW opcode is not properly protected against function interruptions, which can be exploited to disclose potentially sensitive information.
25) An error exists in the default session serializer when processing assignments to session variables having user defined names. This can be exploited to potentially inject arbitrary serialized values into a session by including the PS_UNDEF_MARKER ('!') character in variable names.
Successful exploitation of this vulnerability may allow execution of arbitrary PHP code.
26) The implementation of the "uasort()" function is not properly protected against function interruptions, which can be exploited to trigger a memory corruption and cause a crash.
27) The implementation of the "preg_match()" function is not properly protected against function interruptions, which can be exploited to disclose potentially sensitive information.
28) The implementation of the "strrchr()" function is not properly protected against function interruptions, which can be exploited to disclose potentially sensitive information.
The vulnerabilities are reported in PHP 5.2.13 and 5.3.2. Other versions may also be affected.
Solution:
Update to version 5.2.14, which fixes e.g. vulnerabilities #1, #2, #15, #18 (partially), and #28, or version 5.3.3, which fixes e.g. vulnerabilities #1, #19, #22, and #26.
Further details available to Secunia VIM customers
Provided and/or discovered by:
1-27) Stefan Esser
28) Péter Veres
Original Advisory:
1) http://php-security.org/2010/05/03/mops-2010-006-php-addcslashes-interruption-information-leak-vulnerability/index.html
2) http://php-security.org/2010/05/04/mops-2010-008-php-chunk_split-interruption-information-leak-vulnerability/index.html
3) http://php-security.org/2010/05/06/mops-2010-010-php-html_entity_decode-interruption-information-leak-vulnerability/index.html
4) http://php-security.org/2010/05/18/mops-2010-032-php-iconv_mime_decode-interruption-information-leak-vulnerability/index.html
5) http://php-security.org/2010/05/18/mops-2010-033-php-iconv_substr-interruption-information-leak-vulnerability/index.html
6) http://php-security.org/2010/05/18/mops-2010-034-php-iconv_mime_encode-interruption-information-leak-vulnerability/index.html
7) http://php-security.org/2010/05/21/mops-2010-036-php-htmlentities-and-htmlspecialchars-interruption-information-leak-vulnerability/index.html
8) http://php-security.org/2010/05/21/mops-2010-037-php-str_getcsv-interruption-information-leak-vulnerability/index.html
9) http://php-security.org/2010/05/21/mops-2010-038-php-http_build_query-interruption-information-leak-vulnerability/index.html
10) http://php-security.org/2010/05/21/mops-2010-039-php-strpbrk-interruption-information-leak-vulnerability/index.html
11) http://php-security.org/2010/05/21/mops-2010-040-php-strtr-interruption-information-leak-vulnerability/index.html
12) http://php-security.org/2010/05/26/mops-2010-046-php-str_pad-interruption-information-leak-vulnerability/index.html
13) http://php-security.org/2010/05/26/mops-2010-045-php-str_word_count-interruption-information-leak-vulnerability/index.html
14) http://php-security.org/2010/05/26/mops-2010-044-php-wordwrap-interruption-information-leak-vulnerability/index.html
15) http://php-security.org/2010/05/26/mops-2010-043-php-strtok-interruption-information-leak-vulnerability/index.html
16) http://php-security.org/2010/05/26/mops-2010-042-php-setcookie-interruption-information-leak-vulnerability/index.html
17) http://php-security.org/2010/05/26/mops-2010-041-php-strip_tags-interruption-information-leak-vulnerability/index.html
18) http://php-security.org/2010/05/30/mops-2010-047-php-trimltrimrtrim-interruption-information-leak-vulnerability/index.html
19) http://php-security.org/2010/05/30/mops-2010-048-php-substr_replace-interruption-information-leak-vulnerability/index.html
20) http://php-security.org/2010/05/31/mops-2010-049-php-parse_str-interruption-memory-corruption-vulnerability/index.html
21) http://php-security.org/2010/05/31/mops-2010-054-php-zend_concatzend_assign_concat-opcode-interruption-information-leak-and-memory-corruption-vulnerability/index.html
22) http://php-security.org/2010/05/31/mops-2010-052-php-pack-interruption-information-leak-vulnerability/index.html
23) http://php-security.org/2010/05/31/mops-2010-051-php-unpack-interruption-information-leak-vulnerability/index.html
24) http://php-security.org/2010/05/31/mops-2010-053-php-zend_fetch_rw-opcode-interruption-information-leak-vulnerability/index.html
25) http://php-security.org/2010/05/31/mops-2010-060-php-session-serializer-session-data-injection-vulnerability/index.html
26) http://php-security.org/2010/05/31/mops-2010-055-php-arrayobjectuasort-interruption-memory-corruption-vulnerability/index.html
27) http://php-security.org/2010/05/31/mops-2010-050-php-preg_match-interruption-information-leak-vulnerability/index.html
28) http://www.openwall.com/lists/oss-security/2010/06/30/6
PHP:
http://www.php.net/archive/2010.php#id2010-07-22-1
http://www.php.net/archive/2010.php#id2010-07-22-2
Deep Links:
Links available to Secunia VIM customers
Please provide information about patches, mitigating factors, new versions, exploits, faulty patches, links, and other relevant data by posting comments to this Advisory. You can also send this information to vuln@secunia.com
Subject: PHP Session Data Injection and Function Interruption Vulnerabilities
|
No posts yet |
|
You must be logged in to post a comment. |
Not a customer already?Learn more about how our market leading Vulnerability Management solutions can help you manage risk and ensure compliance. |