|
IntelliTamper Buffer Overflow Vulnerabilities
|
|
Secunia Advisory:
|
SA20172
|
|
|
Release Date:
|
2006-05-19
|
|
Last Update:
|
2008-08-13
|
|
Popularity:
|
6,173 views
|
|
|
Critical:
|
Highly critical
|
|
Impact:
|
System access
|
|
Where:
|
From remote
|
|
Solution Status:
|
Unpatched
|
|
| Software: | IntelliTamper 2.x
|
|
|
Binary Analysis:
|
BA521 :: Available for 1 Credit 
BA522 :: Available for 1 Credit
BA510 :: Available for 1 Credit
BA523 :: Available for 1 Credit
|
|
|
Subscribe:
|
Instant alerts on relevant vulnerabilities
|
|
| CVE reference: | CVE-2006-2494
CVE-2008-3360
CVE-2008-3361
CVE-2008-3583
|
|
Description:
Some vulnerabilities have been discovered in IntelliTamper, which can be exploited by malicious people to compromise a user's system.
1) A boundary error when reading map files (".map") can be exploited to cause a stack-based buffer overflow via a map file containing an overly long line (greater than 4096 bytes).
2) A boundary error when reading map files can be exploited to cause a stack-based buffer overflow via a map file containing an overly long "FOLDER##" line (greater than 480 bytes).
3) Boundary errors when scanning web pages can be exploited to cause stack-based buffer overflows via a web page containing certain HTML tags with an overly long attribute or value (greater than 512 bytes).
4) A boundary error when processing HTTP responses of a scanned site can be exploited to cause a stack-based buffer overflow via a specially crafted HTTP response with an overly long "Server", "Date", "Content-Type", "Set-Cookie", "Content-Length", "Last-Modified", or "Location" header (greater than 512 bytes).
5) A boundary error when processing responses of a scanned site can be exploited to cause a heap-based buffer overflow via a specially crafted, overly long response (greater than 4096 bytes).
Successful exploitation allows execution of arbitrary code.
The vulnerabilities are confirmed in version 2.07. Other versions may also be affected.
Solution:
Do not open site map files (".map") originating from untrusted sources.
Use another product.
Provided and/or discovered by:
1) Devil00
2, 3) Guido Landi
4) Koshi
Changelog:
2006-05-25: Added CVE reference.
2008-07-22: Added vulnerabilities #2 and #3. Updated criticality and "Solution" section. Added links in "Original Advisory" section.
2008-07-23: Added vulnerability #4, updated credits, and added additional link in "Original Advisory" section.
2008-07-23: Updated vulnerability #3 based on additional research by Secunia Research.
2008-07-24: Added vulnerability #5 and updated vulnerability #4 based on additional research by Secunia Research.
2008-08-01: Added CVE reference.
2008-08-13: Added CVE reference.
Original Advisory:
http://milw0rm.com/exploits/6103
http://milw0rm.com/exploits/6106
http://milw0rm.com/exploits/6118
|
|
|
Track this Secunia Advisory
|
Customers of the Secunia Vulnerability Intelligence solutions will automatically receive updates when new information regarding this advisory is released.
Read more about our Vulnerability Intelligence solutions and what they can do for you and your company.
|
|
|
About this Secunia Advisory
|
Please note: The information that this Secunia Advisory is based on comes from a third party unless stated otherwise.
Secunia collects, validates, and verifies all vulnerability reports issued by security research groups, vendors, and others.
|
