mantisbt: Authentication Bypass by Primary Weakness
CVE-2024-34077 is a high-severity authentication bypass by primary weakness vulnerability in mantisbt, with a CVSS 3.1 base score of 7.3 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected mantisbt versions: < 2.26.2. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.19% chance of exploitation within 30 days, higher than 68% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of mantisbt you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- LowSome restricted data can be read.
- Integrity
- LowLimited modification of data is possible.
- Availability
- LowPerformance or availability is reduced.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.3 | High | CNA (github.com) |
| CVSS 3.1 | 7.3 | High | NVD |
Official description
MantisBT (Mantis Bug Tracker) is an open source issue tracker. Insufficient access control in the registration and password reset process allows an attacker to reset another user's password and takeover their account, if the victim has an incomplete request pending. The exploit is only possible while the verification token is valid, i.e for 5 minutes after the confirmation URL sent by e-mail has been opened, and the user did not complete the process by updating their password. A brute-force attack calling account_update.php with increasing user IDs is possible. A successful takeover would grant the attacker full access to the compromised account, including sensitive information and functionalities associated with the account, the extent of which depends on its privileges and the data it has access to. Version 2.26.2 contains a patch for the issue. As a workaround, one may mitigate the risk by reducing the verification token's validity (change the value of the `TOKEN_EXPIRY_AUTHENTICATED` constant in `constants_inc.php`).
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Authentication Bypass by Primary Weakness
The authentication algorithm is sound, but the implemented mechanism can be bypassed as the result of a separate weakness that is primary to the authentication error.
More Authentication Bypass by Primary Weakness vulnerabilities (CWE-305)
Timeline
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Advisories
- github.com/mantisbt/mantisbt/security/advisories/GHSA-93x3-m7pw-ppqmExploit, Issue Tracking, Mitigation
- mantisbt.org/bugs/view.php?id=34433Exploit, Issue Tracking
Patches and release notes
Other vulnerabilities in mantisbt
- 9.3 Critical severity
- 7.5 High severity
- 8.6 High severity
- 7.2 High severity
- 7.5 High severity
- 7.6 High severity
Recent Authentication Bypass by Primary Weakness vulnerabilities
- 7.5 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 7.8 High severity
Spotted an error? Tell us.