Heap-based buffer overflow in libxml2, as used in Google Chrome before 16.0.912.75, allows remote attackers to cause a denial of service or…
Heap-based buffer overflow in libxml2, as used in Google Chrome before 16.0.912.75, allows remote attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors.
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
https://cwe.mitre.org/data/definitions/122.html →Open in CWE collection →The product writes data past the end, or before the beginning, of the intended buffer.
https://cwe.mitre.org/data/definitions/787.html →Open in CWE collection →This attack forces an integer variable to go out of range. The integer variable is often used as an offset such as size of memory allocation or similarly. The attacker would typically control the value of such variable and try to get it out of range. For instance the integer in question is incremented past the maximum possible value, it may wrap to become a very small, or negative number, therefore providing a very incorrect value which can lead to unexpected behavior. At worst the attacker can execute arbitrary code.
https://capec.mitre.org/data/definitions/92.html →Open in CAPEC collection →| Product | Vendor | Status |
|---|---|---|
| chromium-browser | Tracked | |
| chromium-browser | Tracked | |
| libxml2 | Tracked | |
| libxml2 | Tracked | |
| libxml2 | Tracked | |
| libxml2 | Tracked | |
| libxml2 | Tracked | |
| libxml2 | Tracked | |
| mingw32-libxml2 | Tracked | |
| chrome | * | Tracked |
| debian_linux | * | Tracked |
| enterprise_linux_desktop | * | Tracked |
| enterprise_linux_server | * | Tracked |
| enterprise_linux_server_eus | * | Tracked |
| enterprise_linux_workstation | * | Tracked |
| iphone_os | * | Tracked |
| linux_enterprise_server | * | Tracked |
| mac_os_x | * | Tracked |