CVE-2024-34077

{"id": "CVE-2024-34077", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.3, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "LOW", "privilegesRequired": "NONE", "confidentialityImpact": "LOW"}, "impactScore": 3.4, "exploitabilityScore": 3.9}, {"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.3, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "LOW", "privilegesRequired": "NONE", "confidentialityImpact": "LOW"}, "impactScore": 3.4, "exploitabilityScore": 3.9}]}, "published": "2024-05-14T15:38:28.583", "references": [{"url": "https://github.com/mantisbt/mantisbt/commit/92d11a01b195a1b6717a2f205218089158ea6d00", "tags": ["Patch"], "source": "security-advisories@github.com"}, {"url": "https://github.com/mantisbt/mantisbt/security/advisories/GHSA-93x3-m7pw-ppqm", "tags": ["Exploit", "Issue Tracking", "Mitigation", "Patch", "Vendor Advisory"], "source": "security-advisories@github.com"}, {"url": "https://mantisbt.org/bugs/view.php?id=34433", "tags": ["Exploit", "Issue Tracking", "Vendor Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/mantisbt/mantisbt/commit/92d11a01b195a1b6717a2f205218089158ea6d00", "tags": ["Patch"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/mantisbt/mantisbt/security/advisories/GHSA-93x3-m7pw-ppqm", "tags": ["Exploit", "Issue Tracking", "Mitigation", "Patch", "Vendor Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://mantisbt.org/bugs/view.php?id=34433", "tags": ["Exploit", "Issue Tracking", "Vendor Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-305"}, {"lang": "en", "value": "CWE-620"}]}, {"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "NVD-CWE-Other"}]}], "descriptions": [{"lang": "en", "value": "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`)."}, {"lang": "es", "value": "MantisBT (Mantis Bug Tracker) es un rastreador de problemas de c\u00f3digo abierto. Un control de acceso insuficiente en el proceso de registro y restablecimiento de contrase\u00f1a permite a un atacante restablecer la contrase\u00f1a de otro usuario y tomar control de su cuenta, si la v\u00edctima tiene una solicitud incompleta pendiente. El exploit solo es posible mientras el token de verificaci\u00f3n sea v\u00e1lido, es decir, durante 5 minutos despu\u00e9s de que se haya abierto la URL de confirmaci\u00f3n enviada por correo electr\u00f3nico y el usuario no haya completado el proceso actualizando su contrase\u00f1a. Es posible un ataque de fuerza bruta llamando a account_update.php con ID de usuario cada vez mayores. Una toma de control exitosa le otorgar\u00eda al atacante acceso completo a la cuenta comprometida, incluida la informaci\u00f3n confidencial y las funcionalidades asociadas con la cuenta, cuyo alcance depende de sus privilegios y de los datos a los que tiene acceso. La versi\u00f3n 2.26.2 contiene un parche para el problema. Como workaround, se puede mitigar el riesgo reduciendo la validez del token de verificaci\u00f3n (cambie el valor de la constante `TOKEN_EXPIRY_AUTHENTICATED` en `constants_inc.php`)."}], "lastModified": "2025-01-16T16:40:04.230", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:mantisbt:mantisbt:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "3EEBB443-A324-42A1-9D56-638BBE9702A4", "versionEndExcluding": "2.26.2"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}