Apache Archiva 1.3.9 - Multiple Cross-Site Request Forgery Vulnerabilities

Julien Ahrens 2016-07-13 webapps xml
RCE Security Advisory

Product:        Apache Archiva
Vendor URL:     https://archiva.apache.org
Type:           Cross-Site Request Forgery [CWE-253]
Date found:     2016-05-31
Date published: 2016-07-11
CVSSv3 Score:   5.4 (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N)
CVE:            CVE-2016-4469

This vulnerability was discovered and researched by Julien Ahrens from
RCE Security.

Apache Archiva v1.3.9
older versions may be affected too.

Apache Archiva™ is an extensible repository management software that helps
taking care of your own personal or enterprise-wide build artifact
repository. It is the perfect companion for build tools such as Maven,
Continuum, and ANT.

(from the vendor's homepage)

The application basically offers a Cross-Site Request Forgery protection
using the a Struts-based token called "token". While many administrative
functionalities like adding new users are protected on this way, the
following HTTP POST-based functions are missing this token and are
therefore vulnerable to CSRF:

Adding new repository proxy connectors:

Adding new repositories:

Editing existing repositories:

Adding legacy artifact paths:

Changing the organizational appearance:

Uploading new artifacts:

The following Proof-of-Concept triggers this vulnerability and adds a new
proxy connector called "CSRF":

6. RISK ======= To successfully exploit this vulnerability a user with administrative rights must be tricked into visiting an arbitrary website while having an authenticated session in the application. The vulnerability allows remote attackers to perform sensitive administrative actions like adding new repository proxy connectors, adding new repositories, editing existing repositories, adding legacy artifact paths, changing the organizational appearance or uploading new artifacts in the authentication context of the targeted user. 7. SOLUTION =========== Upgrade/Migrate to Apache Archiva 2.2.1 8. REPORT TIMELINE ================== 2016-05-31: Discovery of the vulnerability 2016-05-31: Notified vendor via public security mail address 2016-06-06: No response, sent out another notification 2016-06-10: Vendor states that this version is out of support 2016-06-21: Vendor assigns CVE-2016-4469 2016-07-11: Advisory released 9. REFERENCES ============= https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4469