dbcve.org
ArchivaApplication · Apache

CVE-2024-27140

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
** UNSUPPORTED WHEN ASSIGNED ** Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Apache Archiva. This issue affects Apache Archiva: from 2.0.0. As this project is retired, we do not plan to release a version that fixes this issue. Users are recommended to find an alternative or restrict access to the instance to trusted users. Alternatively, you could configure a HTTP proxy in front of your Archiva instance to only forward requests that do not have malicious characters in the URL. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

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 · moderate confidence

Cross-site Scripting (XSS) vulnerability in Apache Archiva allows improper neutralization of input during web page generation, enabling attackers to inject malicious scripts. Affects versions 2.0.0 and later.

MitigationSince Apache Archiva is retired with no fix planned, organizations should migrate to an alternative solution, restrict network access to trusted users only, or deploy an HTTP proxy to filter malicious characters in requests.

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
ArchivaApplication
Affected:>= 2.0.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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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. Locate Apache Archiva installation
    Search for Archiva directories (typically in /opt/archiva, /usr/share/archiva, or a custom install path) or check running processes for 'archiva' or 'jetty' related to Archiva.
    Affected if Archiva process or installation directory is found on the system
  2. Identify installed version
    Check version file in the installation directory, commonly found as 'archiva-version.txt' in the root or conf directory, or examine the WAR file version metadata.
    Affected if Version resolved is 2.0.0 or higher
  3. Confirm web interface is exposed
    Check network listeners (netstat, ss, or lsof) for ports 8080, 8081, or configured Archiva ports, and review server.xml or jetty.xml for active connector definitions.
    Affected if Web application port is listening and accessible to users or attackers
  4. Verify application is active
    Access the base URL (e.g., http://localhost:8080/archiva) via curl or wget to confirm the application responds with HTML content.
    Affected if HTTP response returns Archiva login or dashboard page, confirming the XSS-prone web interface is operational

If Apache Archiva version 2.0.0 or higher is installed and its web interface is accessible, the environment is affected by this XSS vulnerability.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since Apache Archiva is retired with no fix planned, organizations should migrate to an alternative solution, restrict network access to trusted users only, or deploy an HTTP proxy to filter malicious characters in requests.

Recommended fix High confidence
  1. 1. Restrict network access to the Apache Archiva instance to trusted users only, as the vulnerability can be exploited by untrusted users.
  2. 2. Deploy an HTTP proxy (such as Nginx, Apache HTTP Server with mod_security, or a WAF) in front of the Archiva instance.
  3. 3. Configure the HTTP proxy to filter requests containing potentially malicious characters in the URL, such as: <script>, javascript:, onerror=, and other XSS vectors.
  4. 4. Implement URL validation rules that reject requests with special characters commonly used in XSS attacks (e.g., <, >, ", ', =, ;).
  5. 5. Consider migrating to an actively maintained alternative repository manager (such as Nexus Repository, Artifactory, or GitHub Packages) as Apache Archiva is retired and will not receive security updates.
Caveat No upgrade path available - Apache Archiva project is retired with no planned security fixes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Archiva Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-27140 — 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-2024-27140 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