dbcve.org
ArchivaApplication · Apache

CVE-2022-29405

MEDIUM · 6.5 CVSS v3.1 Published 2022-05-25
Fix available
A fix is available. Upgrade to 2.2.8 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
In Apache Archiva, any registered user can reset password for any users. This is fixed in Archiva 2.2.8

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

A broken access control vulnerability in Apache Archiva allows any authenticated (registered) user to reset passwords for other user accounts. The application fails to properly authorize password reset requests, enabling horizontal privilege escalation where one user can modify another user's credentials.

MitigationUpgrade to Apache Archiva 2.2.8 or later to patch the broken access control vulnerability in the password reset functionality.

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.2.8

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

CVSS:3.1/AV:N/AC:L/PR:L/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 Apache Archiva installation
    Locate the Archiva web application installation directory or check running services on the system
    Affected if Apache Archiva is present on the system
  2. Determine installed version
    Check the Archiva version displayed in the web application footer, in the startup logs, or in the product documentation file (VERSION or RELEASE_NOTES file in the installation directory)
    Affected if The version number is lower than 2.2.8 (for example, 2.2.7, 2.2.6, 2.2.5, etc.)
  3. Verify user authentication is enabled
    Check if the Archiva security realm is configured to allow user login, typically found in the security configuration panel or the users.xml / security.xml configuration file
    Affected if User authentication is enabled and users can register or log in to the application
  4. Confirm password reset feature is accessible
    Attempt to access the password reset endpoint (typically /PasswordReset.action or similar) while logged in as a regular authenticated user, or examine the security configuration for password reset authorization settings
    Affected if The password reset functionality allows any authenticated user to submit a reset request for another user account

If Apache Archiva version is less than 2.2.8 and user authentication is enabled, the application is affected by this broken access control vulnerability allowing horizontal privilege escalation.

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
Upgrade available Upgrade to 2.2.8 or later
Fixed in 2.2.8
Interim mitigation

Upgrade to Apache Archiva 2.2.8 or later to patch the broken access control vulnerability in the password reset functionality.

Recommended fix High confidence

Archiva 2.2.8

  1. 1. Back up your existing Apache Archiva installation directory, configuration files, and database/repository data
  2. 2. Download Apache Archiva 2.2.8 from the official Apache archive at archiva.apache.org/download.cgi
  3. 3. Stop the currently running Archiva service
  4. 4. Replace the existing Archiva installation with the new 2.2.8 version files
  5. 5. Restore your backed-up configuration files (注意: verify configuration compatibility with 2.2.8)
  6. 6. Start the Archiva service
  7. 7. Verify that the password reset functionality now requires appropriate administrative privileges

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

Fix this in Archiva Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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