# CVE-2024-27139: Apache Archiva: incorrect authentication potentially leading to account takeover

> Unauthenticated attackers can modify account data in Apache Archiva, potentially leading to account takeover; users should migrate as the project is retired.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Mar 2024
- **Updated:** 16 Apr 2025
- **Also known as:** GHSA-h595-vwhc-3xwx

## What is CVE-2024-27139?

CVE-2024-27139 is a high-severity missing authorization vulnerability in Apache Archiva, published on 1 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

** UNSUPPORTED WHEN ASSIGNED **

Incorrect Authorization vulnerability in Apache Archiva: a vulnerability in Apache Archiva allows an unauthenticated attacker to modify account data, potentially leading to account takeover.

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.

NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2024-27139?

2 open source packages ship an affected version, including org.apache.archiva:archiva. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.archiva:archiva` | Maven | From 2.0.0 to 2.2.10 | None |
| `org.apache.archiva:archiva` | Maven | From 2.0.0 to 2.2.10 | None |

Products: Apache Archiva.

## How do I fix CVE-2024-27139?

No fix has been published for CVE-2024-27139 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-27139 being exploited?

There is no known exploitation of CVE-2024-27139 in the wild and no public exploit code.

## Other vulnerabilities in Apache Archiva

- [CVE-2013-2251](https://insights.sbomify.com/CVE-2013-2251/): Apache Struts Improper Input Validation (critical 9.8, exploited in the wild)
- [CVE-2016-4469](https://insights.sbomify.com/CVE-2016-4469/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2017-5657](https://insights.sbomify.com/CVE-2017-5657/): Apache Archiva vulnerable to Cross Site Request Forgery (high 8.0)
- [CVE-2024-27138](https://insights.sbomify.com/CVE-2024-27138/): Apache Archiva: disabling user registration is not effective (high 7.5)
- [CVE-2022-40308](https://insights.sbomify.com/CVE-2022-40308/): Apache Archiva prior to 2.2.9 may allow the anonymous user to read arbitrary files (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-27139 and fix it if it is affected.

What it is: CVE-2024-27139 is a high-severity missing authorization vulnerability in Apache Archiva, published on 1 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-27139 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.archiva:archiva (Maven): affected from 2.0.0 up to 2.2.10; no fix listed
- org.apache.archiva:archiva (Maven): affected from 2.0.0 up to 2.2.10; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-27139/ (Markdown: https://insights.sbomify.com/CVE-2024-27139/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-27139
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-27139
- OSV: https://osv.dev/vulnerability/CVE-2024-27139

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-27139/
Summaries are generated and may contain mistakes; the official description above is the record.