dbcve.org
JackrabbitApplication · Apache

CVE-2016-6801

HIGH · 8.8 CVSS v3.0 Published 2016-09-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cross-site request forgery (CSRF) vulnerability in the CSRF content-type check in Jackrabbit-Webdav in Apache Jackrabbit 2.4.x before 2.4.6, 2.6.x before 2.6.6, 2.8.x before 2.8.3, 2.10.x before 2.10.4, 2.12.x before 2.12.4, and 2.13.x before 2.13.3 allows remote attackers to hijack the authentication of unspecified victims for requests that create a resource via an HTTP POST request with a (1) missing or (2) crafted Content-Type header.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

CSRF vulnerability in Apache Jackrabbit's WebDAV component allows attackers to bypass the Content-Type-based CSRF check by submitting HTTP POST requests with missing or crafted Content-Type headers, enabling authentication hijacking for resource creation requests.

MitigationUpgrade to Apache Jackrabbit version 2.4.6, 2.6.6, 2.8.3, 2.10.4, 2.12.4, or 2.13.3 or later. Alternatively, implement additional CSRF protections such as anti-CSRF tokens or SameSite cookie attributes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JackrabbitApplication
Affected:= 2.4.0= 2.4.1= 2.4.2= 2.4.3= 2.4.4= 2.4.5= 2.6.0= 2.6.1= 2.6.2= 2.6.3= 2.6.4= 2.6.5
Debian LinuxOperating system
Affected:= 8.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Jackrabbit installation and version
    Locate the jackrabbit-core jar file in your deployment directory or check the version reported in the Jackrabbit web console. On Debian systems, check /usr/share/jackrabbit or your application lib directory for jackrabbit-*.jar files.
    Affected if The installed version matches 2.4.0 through 2.4.5, or 2.6.0 through 2.6.5, or is Debian 8.0 with bundled Jackrabbit in these version ranges.
  2. Verify WebDAV component is enabled
    Inspect your web.xml deployment descriptor (typically in WEB-INF/web.xml) or your servlet container configuration for a mapping to the WebDAV servlet (look for DavServlet or similar /repository/ path mappings). Check if HTTP POST requests to WebDAV endpoints are accepted.
    Affected if The DavServlet is mapped and active, accepting POST requests to WebDAV URLs such as /repository/server/ or /dav/.
  3. Inspect CSRF protection configuration for WebDAV
    Review the WebDAV servlet configuration in web.xml or the Jackrabbit configuration file for CSRFFilter or CSRFPreventionFilter settings. Look for rules that rely on Content-Type header validation (such as checking for application/xml, text/xml, or other MIME types).
    Affected if The CSRF protection is configured to allow requests based solely on Content-Type header values, and your deployment accepts POST requests with missing or non-standard Content-Type headers to WebDAV endpoints.
  4. Test for vulnerable request handling
    Send a POST request to your WebDAV endpoint (e.g., /repository/server/) with no Content-Type header or a crafted value such as text/plain, and observe if the request is processed without additional CSRF token validation.
    Affected if The server accepts and processes the POST request without requiring anti-CSRF tokens, indicating the Content-Type-based check can be bypassed.

You are affected if Apache Jackrabbit version 2.4.0-2.4.5 or 2.6.0-2.6.5 is running with the WebDAV component enabled and the CSRF protection relies on Content-Type header validation that can be bypassed via missing or crafted headers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Apache Jackrabbit version 2.4.6, 2.6.6, 2.8.3, 2.10.4, 2.12.4, or 2.13.3 or later. Alternatively, implement additional CSRF protections such as anti-CSRF tokens or SameSite cookie attributes.

Fix this in Jackrabbit Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-6801 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-6801 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data