CVE-2016-6801: CSRF

Published Sep 21, 2016
·
Updated

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.

Affected Software

35 affected componentsFixes available
maven/org.apache.jackrabbit:jackrabbit-webdav>=2.13.0<2.13.3
2.13.3
maven/org.apache.jackrabbit:jackrabbit-webdav>=2.12.0<2.12.4
2.12.4
maven/org.apache.jackrabbit:jackrabbit-webdav>=2.10.0<2.10.4
2.10.4
maven/org.apache.jackrabbit:jackrabbit-webdav>=2.8.0<2.8.3
2.8.3
maven/org.apache.jackrabbit:jackrabbit-webdav>=2.6.0<2.6.6
2.6.6
maven/org.apache.jackrabbit:jackrabbit-webdav>=2.4.0<2.4.6
2.4.6
Apache jackrabbit=2.4.0
Apache jackrabbit=2.4.1
Apache jackrabbit=2.4.2
Apache jackrabbit=2.4.3
Apache jackrabbit=2.4.4
Apache jackrabbit=2.4.5
Apache jackrabbit=2.6.0
Apache jackrabbit=2.6.1
Apache jackrabbit=2.6.2
Apache jackrabbit=2.6.3
Apache jackrabbit=2.6.4
Apache jackrabbit=2.6.5
Apache jackrabbit=2.8.0
Apache jackrabbit=2.8.1
Apache jackrabbit=2.8.2
Apache jackrabbit=2.10.0
Apache jackrabbit=2.10.1
Apache jackrabbit=2.10.2
Apache jackrabbit=2.10.3
Apache jackrabbit=2.12.0
Apache jackrabbit=2.12.1
Apache jackrabbit=2.12.2
Apache jackrabbit=2.12.3
Apache jackrabbit=2.13.0
Apache jackrabbit=2.13.1
Apache jackrabbit=2.13.2
Debian Debian Linux=8.0
ubuntu/jackrabbit<2.3.6-1+deb8u2build0.14.04.1
2.3.6-1+deb8u2build0.14.04.1
ubuntu/jackrabbit<2.10.1-2ubuntu0.1~esm1
2.10.1-2ubuntu0.1~esm1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/org.apache.jackrabbit:jackrabbit-webdav to a version that resolves this vulnerability.

    Fixed in 2.13.3
  2. Upgrade

    Upgrade maven/org.apache.jackrabbit:jackrabbit-webdav to a version that resolves this vulnerability.

    Fixed in 2.12.4
  3. Upgrade

    Upgrade maven/org.apache.jackrabbit:jackrabbit-webdav to a version that resolves this vulnerability.

    Fixed in 2.10.4
  4. Upgrade

    Upgrade maven/org.apache.jackrabbit:jackrabbit-webdav to a version that resolves this vulnerability.

    Fixed in 2.8.3
  5. Upgrade

    Upgrade maven/org.apache.jackrabbit:jackrabbit-webdav to a version that resolves this vulnerability.

    Fixed in 2.6.6
  6. Upgrade

    Upgrade maven/org.apache.jackrabbit:jackrabbit-webdav to a version that resolves this vulnerability.

    Fixed in 2.4.6
  7. Upgrade

    Upgrade ubuntu/jackrabbit to a version that resolves this vulnerability.

    Fixed in 2.3.6-1+deb8u2build0.14.04.1
  8. Upgrade

    Upgrade ubuntu/jackrabbit to a version that resolves this vulnerability.

    Fixed in 2.10.1-2ubuntu0.1~esm1

Event History

Sep 21, 2016
CVE Published
via MITRE·02:00 PM
Data Sourced
via MITRE·02:00 PM
Description
Data Sourced
via OSV·02:25 PM
DescriptionSeverityAffected Software
May 17, 2022
Advisory Published
03:48 AM

Frequently Asked Questions

1

What is the severity of CVE-2016-6801?

CVE-2016-6801 is considered a high-severity vulnerability due to its potential for cross-site request forgery (CSRF), allowing remote attackers to hijack user sessions.

2

How do I fix CVE-2016-6801?

To fix CVE-2016-6801, upgrade your Apache Jackrabbit-Webdav to version 2.13.3 or later for the 2.13.x series, 2.12.4 or later for the 2.12.x series, or respective later versions for others.

3

Which versions of Apache Jackrabbit are affected by CVE-2016-6801?

CVE-2016-6801 affects 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.

4

What types of attacks can exploit CVE-2016-6801?

CVE-2016-6801 can be exploited using cross-site request forgery (CSRF) techniques, allowing attackers to perform unauthorized actions on behalf of authenticated users.

5

Is there a workaround for CVE-2016-6801 if I cannot upgrade?

While the recommended solution is to upgrade, implementing strict content-type validation and CSRF protections can serve as temporary mitigations against CVE-2016-6801.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203