# CVE-2008-1767: Memory corruption in n/a > A buffer overflow in libxslt allows attackers to cause a crash or execute arbitrary code via a malicious XSL style sheet. - **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 23 May 2008 - **Updated:** 7 Aug 2024 - **Also known as:** DEBIAN-CVE-2008-1767, DSA-1589-1, GHSA-h927-jfxh-4j78, RHSA-2008:0287 ## What is CVE-2008-1767? CVE-2008-1767 is a high-severity memory corruption vulnerability in Redhat Enterprise Linux, published on 23 May 2008. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description Buffer overflow in pattern.c in libxslt before 1.1.24 allows context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via an XSL style sheet file with a long XSLT "transformation match" condition that triggers a large number of steps. Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) ## Which versions are affected by CVE-2008-1767? It affects 5 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libxslt` | Red Hat:enterprise_linux:2.1::as | All versions | 0:1.0.15-3 | | `libxslt-devel` | Red Hat:enterprise_linux:2.1::as | All versions | 0:1.0.15-3 | | `libxslt-python` | Red Hat:enterprise_linux:2.1::as | All versions | 0:1.0.15-3 | | `libxslt` | Red Hat:enterprise_linux:2.1::aw | All versions | 0:1.0.15-3 | | `libxslt-devel` | Red Hat:enterprise_linux:2.1::aw | All versions | 0:1.0.15-3 | | `libxslt-python` | Red Hat:enterprise_linux:2.1::aw | All versions | 0:1.0.15-3 | | `libxslt` | Red Hat:enterprise_linux:2.1::es | All versions | 0:1.0.15-3 | | `libxslt-devel` | Red Hat:enterprise_linux:2.1::es | All versions | 0:1.0.15-3 | | `libxslt-python` | Red Hat:enterprise_linux:2.1::es | All versions | 0:1.0.15-3 | | `libxslt` | Red Hat:enterprise_linux:2.1::ws | All versions | 0:1.0.15-3 | | `libxslt-devel` | Red Hat:enterprise_linux:2.1::ws | All versions | 0:1.0.15-3 | | `libxslt-python` | Red Hat:enterprise_linux:2.1::ws | All versions | 0:1.0.15-3 | | `libxslt` | Red Hat:enterprise_linux:3::as | All versions | 0:1.0.33-6 | | `libxslt-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:1.0.33-6 | | `libxslt-devel` | Red Hat:enterprise_linux:3::as | All versions | 0:1.0.33-6 | | `libxslt` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.0.33-6 | | `libxslt-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.0.33-6 | | `libxslt-devel` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.0.33-6 | | `libxslt` | Red Hat:enterprise_linux:3::es | All versions | 0:1.0.33-6 | | `libxslt-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:1.0.33-6 | | `libxslt-devel` | Red Hat:enterprise_linux:3::es | All versions | 0:1.0.33-6 | | `libxslt` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.0.33-6 | | `libxslt-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.0.33-6 | | `libxslt-devel` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.0.33-6 | | `libxslt` | Red Hat:enterprise_linux:4::as | All versions | 0:1.1.11-1.el4_6.1 | | `libxslt-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:1.1.11-1.el4_6.1 | | `libxslt-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:1.1.11-1.el4_6.1 | | `libxslt-python` | Red Hat:enterprise_linux:4::as | All versions | 0:1.1.11-1.el4_6.1 | | `libxslt` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.1.11-1.el4_6.1 | | `libxslt-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.1.11-1.el4_6.1 | | `libxslt-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.1.11-1.el4_6.1 | | `libxslt-python` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.1.11-1.el4_6.1 | | `libxslt` | Red Hat:enterprise_linux:4::es | All versions | 0:1.1.11-1.el4_6.1 | | `libxslt-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:1.1.11-1.el4_6.1 | | `libxslt-devel` | Red Hat:enterprise_linux:4::es | All versions | 0:1.1.11-1.el4_6.1 | | `libxslt-python` | Red Hat:enterprise_linux:4::es | All versions | 0:1.1.11-1.el4_6.1 | | `libxslt` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.1.11-1.el4_6.1 | | `libxslt-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.1.11-1.el4_6.1 | | `libxslt-devel` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.1.11-1.el4_6.1 | | `libxslt-python` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.1.11-1.el4_6.1 | Products: Redhat Desktop, Redhat Enterprise Linux, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Desktop Workstation, Redhat Linux Advanced Workstation. ## How do I fix CVE-2008-1767? Upgrade to a fixed version. ## Is CVE-2008-1767 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-1767 exists. Public exploit code: - libxslt XSL 1.1.23 - File Processing Buffer Overflow (exploitdb) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2008-1767 and fix it if it is affected. What it is: CVE-2008-1767 is a high-severity memory corruption vulnerability in Redhat Enterprise Linux, published on 23 May 2008. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-1767 exists. Affected product: Redhat Enterprise Linux. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2008-1767/ (Markdown: https://insights.sbomify.com/CVE-2008-1767/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2008-1767 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2008-1767 - OSV: https://osv.dev/vulnerability/CVE-2008-1767 --- From sbomify Insights: https://insights.sbomify.com/CVE-2008-1767/ Summaries are generated and may contain mistakes; the official description above is the record.