Multiple XSS and CSRF issues in Apache Archiva version 1.3.4. Disclosure blogpost.


When playing around with an installation of Apache Archiva (v1.3.4), I discovered multiple XSS and CSRF issues with the product. I reported these to the vendor and participated in responsible disclosure. This post describes the proof of concept codes and timelines.


Project: Apache Archiva
Severity: High
Versions: 1.3.0 – 1.3.4. The unsupported versions Archiva 1.0 - 1.2.2 are also affected.
Exploit type: Multiple XSS & CSRF
Mitigation: Archiva 1.3.4 and earlier users should upgrade to 1.3.5
Vendor URL:
CVE: CVE-ID-2011-1077, CVE-2011-1026


28 February 2011: Vendor Contacted
1 March 2011: Vendor Response received. CVE-2011-1026 for CSRF Issues Assigned.
7 March 2011: CVE-2011-1077 Assigned for XSS Issues.
14 March 2011: Fixes released to selected channels / Found to be insufficient
27 May 2011: Vendor releases v1.3.5
27 May 2011: Vendor releases security disclosure to Bugtraq and FD.
30 May 2011: Exploit details released on Bugtraq & FD

Product Description

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.

Archiva offers several capabilities, amongst which remote repository proxying, security access management, build artifact storage, delivery, browsing, indexing and usage reporting, extensible scanning functionality… and many more! (Source:

Vulnerability Details

XSS: User can insert HTML or execute arbitrary JavaScript code within the vulnerable application. The vulnerabilities arise due to insufficient input validation in multiple input fields throughout the application.

Successful exploitation of these vulnerabilities could result in, but not limited to, compromise of the application, theft of cookie-based authentication credentials, arbitrary url redirection, disclosure or modification of sensitive data and phishing attacks.

CSRF: These issues allow an attacker to access and use the application with the session of a logged on user. In this case if an administrative account is exploited, total application compromise may be acheived.

An attacker can build a simple html page containing a hidden Image tag (eg: <img src="vulnurl" width="0" height="0">) and entice the administrator to access the page.

Proof of Concept

Reflected XSS







Stored XSS

  • Exploit code: test<script>alert('xss')</script>

Case 1

  • Store URL:
  • Vars:,,Directory:repository.location, Index Directory:repository.indexDir
  • Execute URL:

Case 2

  • Store URL:
  • Vars: Name:organisationName, URL:organisation:URL, LogoURL:organisation:URL
  • Execute URL:

Case 3

  • Store URL:
  • Vars: Path:name=legacyArtifactPath.path, GroupId:groupId, ArtifactId:artifactId, Version:version, Classifier:classifier, Type:type
  • Execute URL:

Case 4

  • Store URL:
  • Vars:, Protocol:proxy.protocol,, Port:proxy.port, Username:proxy.username
  • Execute URL: