# CVE-2015-1833: Improper Input Validation in Apache Jackrabbit > Remote attackers can read arbitrary files and access intranet servers via crafted WebDAV requests in Apache Jackrabbit. - **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 29 May 2015 - **Updated:** 6 Aug 2024 - **Also known as:** DEBIAN-CVE-2015-1833, DSA-3298-1, GHSA-9284-j4c9-779q, MGASA-2015-0242, UBUNTU-CVE-2015-1833 ## What is CVE-2015-1833? CVE-2015-1833 is a medium-severity vulnerability in n/a, published on 29 May 2015. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description XML external entity (XXE) vulnerability in Apache Jackrabbit before 2.0.6, 2.2.x before 2.2.14, 2.4.x before 2.4.6, 2.6.x before 2.6.6, 2.8.x before 2.8.1, and 2.10.x before 2.10.1 allows remote attackers to read arbitrary files and send requests to intranet servers via a crafted WebDAV request. Weakness: CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2015-1833? 12 open source packages ship an affected version, including org.apache.jackrabbit:jackrabbit-core. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.jackrabbit:jackrabbit-core` | Maven | All versions | 2.0.6 | | `org.apache.jackrabbit:jackrabbit-core` | Maven | All versions | 2.0.6 | | `org.apache.jackrabbit:jackrabbit-core` | Maven | From 2.10.0 | 2.10.1 | | `org.apache.jackrabbit:jackrabbit-core` | Maven | From 2.10.0 | 2.10.1 | | `org.apache.jackrabbit:jackrabbit-core` | Maven | From 2.2.0 | 2.2.14 | | `org.apache.jackrabbit:jackrabbit-core` | Maven | From 2.2.0 | 2.2.14 | | `org.apache.jackrabbit:jackrabbit-core` | Maven | From 2.4.0 | 2.4.6 | | `org.apache.jackrabbit:jackrabbit-core` | Maven | From 2.4.0 | 2.4.6 | | `org.apache.jackrabbit:jackrabbit-core` | Maven | From 2.6.0 | 2.6.6 | | `org.apache.jackrabbit:jackrabbit-core` | Maven | From 2.6.0 | 2.6.6 | | `org.apache.jackrabbit:jackrabbit-core` | Maven | From 2.8.0 | 2.8.1 | | `org.apache.jackrabbit:jackrabbit-core` | Maven | From 2.8.0 | 2.8.1 | Products: Apache Jackrabbit. ## How do I fix CVE-2015-1833? Upgrade org.apache.jackrabbit:jackrabbit-core to a fixed version for your release line: 2.0.6, 2.10.1, 2.2.14 or 2.4.6. ## Is CVE-2015-1833 being exploited? There is no known exploitation of CVE-2015-1833 in the wild and no public exploit code. Public exploit code: - Apache JackRabbit - WebDAV XML External Entity (exploitdb) ## Other vulnerabilities in n/a - [CVE-2023-37895](https://insights.sbomify.com/CVE-2023-37895/): Apache Jackrabbit RMI access can lead to RCE (critical 9.8) - [CVE-2026-92414](https://insights.sbomify.com/CVE-2026-92414/): Apache Jackrabbit: Pre-auth hijack of cached sessions via derivable WebDAV lock tokens (critical 9.3) - [CVE-2025-53689](https://insights.sbomify.com/CVE-2025-53689/): Apache Jackrabbit: XXE vulnerability in jackrabbit-spi-commons (high 8.8) - [CVE-2016-6801](https://insights.sbomify.com/CVE-2016-6801/): Apache Jackrabbit Authentication Hijacking Vulnerability (high 8.8) - [CVE-2026-92415](https://insights.sbomify.com/CVE-2026-92415/): Apache Jackrabbit: DavEx client runs Class.forName + (String)-constructor on server-controlled error bodies (medium 6.9) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2015-1833 and fix it if it is affected. What it is: CVE-2015-1833 is a medium-severity vulnerability in n/a, published on 29 May 2015. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2015-1833 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.jackrabbit:jackrabbit-core (Maven): affected all versions; fixed in 2.0.6 - org.apache.jackrabbit:jackrabbit-core (Maven): affected all versions; fixed in 2.0.6 - org.apache.jackrabbit:jackrabbit-core (Maven): affected from 2.10.0; fixed in 2.10.1 - org.apache.jackrabbit:jackrabbit-core (Maven): affected from 2.10.0; fixed in 2.10.1 - org.apache.jackrabbit:jackrabbit-core (Maven): affected from 2.2.0; fixed in 2.2.14 - org.apache.jackrabbit:jackrabbit-core (Maven): affected from 2.2.0; fixed in 2.2.14 - org.apache.jackrabbit:jackrabbit-core (Maven): affected from 2.4.0; fixed in 2.4.6 - org.apache.jackrabbit:jackrabbit-core (Maven): affected from 2.4.0; fixed in 2.4.6 - org.apache.jackrabbit:jackrabbit-core (Maven): affected from 2.6.0; fixed in 2.6.6 - org.apache.jackrabbit:jackrabbit-core (Maven): affected from 2.6.0; fixed in 2.6.6 - org.apache.jackrabbit:jackrabbit-core (Maven): affected from 2.8.0; fixed in 2.8.1 - org.apache.jackrabbit:jackrabbit-core (Maven): affected from 2.8.0; fixed in 2.8.1 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-2015-1833/ (Markdown: https://insights.sbomify.com/CVE-2015-1833/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2015-1833 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-1833 - OSV: https://osv.dev/vulnerability/CVE-2015-1833 --- From sbomify Insights: https://insights.sbomify.com/CVE-2015-1833/ Summaries are generated and may contain mistakes; the official description above is the record.