CVE-2024-26578: Apache Answer: Repeated submission at registration created duplicate users with the same name

Published Feb 22, 2024
·
Updated

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') vulnerability in Apache Answer. This issue affects Apache Answer through 1.2.1.

Repeated submission during registration resulted in the registration of the same user. When users register, if they rapidly submit multiple registrations using scripts, it can result in the creation of multiple user accounts simultaneously with the same name.

Users are recommended to upgrade to version 1.2.5, which fixes the issue.

Other sources

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') vulnerability in Apache Answer.This issue affects Apache Answer: through 1.2.1.

Repeated submission during registration resulted in the registration of the same user. When users register, if they rapidly submit multiple registrations using scripts, it can result in the creation of multiple user accounts simultaneously with the same name. Users are recommended to upgrade to version [1.2.5], which fixes the issue.

NVD

Affected Software

2 affected componentsFixes available
go/github.com/apache/incubator-answer<1.2.5
1.2.5
Apache Answer<=1.2.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade go/github.com/apache/incubator-answer to a version that resolves this vulnerability.

    Fixed in 1.2.5
  2. Upgrade

    Upgrade Apache Answer to a version that resolves this vulnerability.

    Fixed in 1.2.5
  3. Compensating control

    During registration, avoid rapidly submitting multiple registrations in parallel (e.g., via scripts), as it can cause multiple user accounts with the same name due to a race condition.

Event History

Feb 22, 2024
CVE Published
via MITRE·09:28 AM
Data Sourced
via MITRE·09:28 AM
DescriptionWeakness
Data Sourced
via NVD·10:15 AM
DescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·12:30 PM

Frequently Asked Questions

1

What is the severity of CVE-2024-26578?

CVE-2024-26578 is classified as a critical vulnerability due to its potential impact on user registrations.

2

How do I fix CVE-2024-26578?

To mitigate CVE-2024-26578, upgrade Apache Answer to version 1.2.5 or higher.

3

What are the consequences of CVE-2024-26578?

The consequences of CVE-2024-26578 include the potential for duplicate user registrations, leading to data integrity issues.

4

Which versions of Apache Answer are affected by CVE-2024-26578?

CVE-2024-26578 affects Apache Answer versions up to and including 1.2.1.

5

Who can be impacted by CVE-2024-26578?

Users and administrators of Apache Answer are at risk of being impacted by CVE-2024-26578 due to improper synchronization during user registration.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203