libxslt 1.1.26 and earlier, as used in Google Chrome before 21.0.1180.89, does not properly manage memory, which might allow remote attacke…
libxslt 1.1.26 and earlier, as used in Google Chrome before 21.0.1180.89, does not properly manage memory, which might allow remote attackers to cause a denial of service (application crash) via a crafted XSLT expression that is not properly identified during XPath navigation, related to (1) the xsltCompileLocationPathPattern function in libxslt/pattern.c and (2) the xsltGenerateIdFunction function in libxslt/functions.c.
Weaknesses in this category are related to improper management of system resources.
https://cwe.mitre.org/data/definitions/399.html →Open in CWE collection →The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
https://cwe.mitre.org/data/definitions/416.html →Open in CWE collection →| Product | Vendor | Status |
|---|---|---|
| chromium-browser | Tracked | |
| chromium-browser | Tracked | |
| libxslt | Tracked | |
| libxslt | Tracked | |
| libxslt | Tracked | |
| libxslt | Tracked | |
| chrome | * | Tracked |
| iphone_os | * | Tracked |
| libxslt | * | Tracked |