# CVE-2008-2935: Memory corruption in n/a > Heap-based buffer overflows in libxslt allow attackers to execute arbitrary code via a malicious XML file processed by the application. - **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:** 1 Aug 2008 - **Updated:** 7 Aug 2024 - **Also known as:** DEBIAN-CVE-2008-2935, DSA-1624-1, DTSA-152-1, GHSA-4597-8mcf-pw36, RHSA-2008:0649 ## What is CVE-2008-2935? CVE-2008-2935 is a high-severity memory corruption vulnerability in n/a, published on 1 Aug 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 Multiple heap-based buffer overflows in the rc4 (1) encryption (aka exsltCryptoRc4EncryptFunction) and (2) decryption (aka exsltCryptoRc4DecryptFunction) functions in crypto.c in libexslt in libxslt 1.1.8 through 1.1.24 allow context-dependent attackers to execute arbitrary code via an XML file containing a long string as "an argument in the XSL input." Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) ## Which versions are affected by CVE-2008-2935? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libxslt` | Red Hat:enterprise_linux:4::as | All versions | 0:1.1.11-1.el4_7.2 | | `libxslt-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:1.1.11-1.el4_7.2 | | `libxslt-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:1.1.11-1.el4_7.2 | | `libxslt-python` | Red Hat:enterprise_linux:4::as | All versions | 0:1.1.11-1.el4_7.2 | | `libxslt` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.1.11-1.el4_7.2 | | `libxslt-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.1.11-1.el4_7.2 | | `libxslt-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.1.11-1.el4_7.2 | | `libxslt-python` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.1.11-1.el4_7.2 | | `libxslt` | Red Hat:enterprise_linux:4::es | All versions | 0:1.1.11-1.el4_7.2 | | `libxslt-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:1.1.11-1.el4_7.2 | | `libxslt-devel` | Red Hat:enterprise_linux:4::es | All versions | 0:1.1.11-1.el4_7.2 | | `libxslt-python` | Red Hat:enterprise_linux:4::es | All versions | 0:1.1.11-1.el4_7.2 | | `libxslt` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.1.11-1.el4_7.2 | | `libxslt-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.1.11-1.el4_7.2 | | `libxslt-devel` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.1.11-1.el4_7.2 | | `libxslt-python` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.1.11-1.el4_7.2 | | `libxslt` | Red Hat:enterprise_linux:5::client | All versions | 0:1.1.17-2.el5_2.2 | | `libxslt-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:1.1.17-2.el5_2.2 | | `libxslt-python` | Red Hat:enterprise_linux:5::client | All versions | 0:1.1.17-2.el5_2.2 | | `libxslt` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:1.1.17-2.el5_2.2 | | `libxslt-debuginfo` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:1.1.17-2.el5_2.2 | | `libxslt-devel` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:1.1.17-2.el5_2.2 | | `libxslt` | Red Hat:enterprise_linux:5::server | All versions | 0:1.1.17-2.el5_2.2 | | `libxslt-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:1.1.17-2.el5_2.2 | | `libxslt-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:1.1.17-2.el5_2.2 | | `libxslt-python` | Red Hat:enterprise_linux:5::server | All versions | 0:1.1.17-2.el5_2.2 | Products: Xmlsoft Libxslt. ## How do I fix CVE-2008-2935? Upgrade to a fixed version. ## Is CVE-2008-2935 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-2935 exists. Public exploit code: - libxslt 1.1.x - RC4 Encryption and Decryption functions Buffer Overflow (exploitdb) ## Other vulnerabilities in n/a - [CVE-2024-55549](https://insights.sbomify.com/CVE-2024-55549/): Use after free in libxslt (high 7.8) - [CVE-2025-24855](https://insights.sbomify.com/CVE-2025-24855/): Use after free in libxslt (high 7.8) - [CVE-2015-9019](https://insights.sbomify.com/CVE-2015-9019/): Weak cryptography in n/a (medium 5.3) - [CVE-2013-4520](https://insights.sbomify.com/CVE-2013-4520/): Denial of service in n/a (medium 4.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2008-2935 and fix it if it is affected. What it is: CVE-2008-2935 is a high-severity memory corruption vulnerability in n/a, published on 1 Aug 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-2935 exists. Affected product: n/a. 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-2935/ (Markdown: https://insights.sbomify.com/CVE-2008-2935/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2008-2935 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2008-2935 - OSV: https://osv.dev/vulnerability/CVE-2008-2935 --- From sbomify Insights: https://insights.sbomify.com/CVE-2008-2935/ Summaries are generated and may contain mistakes; the official description above is the record.