Skip to content

Apache Answer Race Condition vulnerability

Moderate severity GitHub Reviewed Published Feb 22, 2024 to the GitHub Advisory Database • Updated Dec 11, 2024

Package

gomod github.com/apache/incubator-answer (Go)

Affected versions

< 1.2.5

Patched versions

1.2.5

Description

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.

References

Published by the National Vulnerability Database Feb 22, 2024
Published to the GitHub Advisory Database Feb 22, 2024
Reviewed Feb 22, 2024
Last updated Dec 11, 2024

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

EPSS score

0.181%
(56th percentile)

Weaknesses

CVE ID

CVE-2024-26578

GHSA ID

GHSA-9q24-hwmc-797x
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.