dbcve.org
ArchivaApplication · Apache

CVE-2024-27138

HIGH · 7.5 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 →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 ** Incorrect Authorization vulnerability in Apache Archiva. Apache Archiva has a setting to disable user registration, however this restriction can be bypassed. As Apache Archiva has been retired, we do not expect to release a version of Apache Archiva that fixes this issue. You are recommended to look into migrating to a different solution, or isolate your instance from any untrusted users. 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 · high confidence

Apache Archiva has a user registration disable setting that can be bypassed due to an incorrect authorization check. This allows unauthorized users to register accounts even when the administrator has explicitly disabled user registration, potentially granting them access to the repository management system.

MitigationSince Apache Archiva is retired and will not receive patches, organizations should migrate to a supported repository management solution or implement strict network isolation to prevent access from untrusted users.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Identify if Apache Archiva is installed
    Check for Archiva installation by looking for the archiva application directory, process named 'archiva', or port 8080/8081 commonly used by Archiva
    Affected if Apache Archiva is present in the environment
  2. Confirm the installed version
    Locate the version file or check the application startup logs for the Archiva version number
    Affected if Version is 2.0.0 or higher
  3. Locate the security configuration
    Check the Archiva configuration files (typically in conf/ or webapps/archiva/WEB-INF/ ) for security-related settings such as user.registration.enabled or similar disable flags
    Affected if User registration disable configuration exists but may be bypassed
  4. Verify the registration disable setting
    Review the configuration to determine if the administrator has explicitly disabled user registration (look for properties like archiva.security.allowRegister or user.registration.disabled)
    Affected if Registration is configured as disabled but the vulnerability allows bypass
  5. Test registration endpoint behavior
    Attempt to access the user registration endpoint or API (typically /security/userregister.action or /signup) to observe if registration proceeds despite the disable setting
    Affected if Registration completes successfully when it should be blocked

Environment is affected if Apache Archiva version 2.0.0 or higher is running and allows user registration to succeed even when an administrator has explicitly disabled the registration feature.

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 and will not receive patches, organizations should migrate to a supported repository management solution or implement strict network isolation to prevent access from untrusted users.

Recommended fix High confidence
  1. Migrate to an alternative solution as Apache Archiva has been retired and no fix will be released.
  2. If migration is not immediately possible, isolate the Apache Archiva instance from any untrusted users to reduce exposure.
  3. Review and implement network-level access controls to limit who can access the Archiva instance.

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

Fix this in Archiva Scoped from the published advisory
  • Consultation12.0 h
  • Implementation32.0 h
  • Testing16.0 h
  • Review / QA8.0 h
68.0 hours of engineering $12,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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