Cyber Resilience

CVE-2023-49619

Race Condition in Apache Answer ≤ 1.2.1

Race Condition
Published
10 January 2024
Modified
11 June 2025
Patch / advisory
View advisory
CVSS Score v3.1 3.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N
EPSS Score 0.0089 56th percentile
Risk Priority 31 floored blend · peak EPSS

Summary

CVE-2023-49619 is a low-severity Race Condition (CWE-362) vulnerability in Apache Answer. Its CVSS base score is 3.1 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 44% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-39 (Process Isolation) and SC-4 (Information in Shared System Resources) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A06:2025 Insecure Design

EU & UK References

Vulnerability Data

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') vulnerability in Apache Answer. This issue affects Apache Answer: through 1.2.0. Under normal circumstances, a user can only bookmark a question once, and will only increase the number of questions…

more

bookmarked once. However, repeat submissions through the script can increase the number of collection of the question many times. Users are recommended to upgrade to version [1.2.1], which fixes the issue.

CWE(s)
CWE-362

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-26578Same product: Apache Answer
CVE-2026-34033Same product: Apache Answer
CVE-2026-60023Same product: Apache Answer
CVE-2026-25700Same product: Apache Answer
CVE-2025-52434Same vendor: Apache
CVE-2024-41888Same product: Apache Answer
CVE-2026-34905Same product: Apache Answer
CVE-2024-41890Same product: Apache Answer
CVE-2024-40761Same product: Apache Answer
CVE-2026-34031Same product: Apache Answer

Affected Assets

apache
answer
≤ 1.2.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V10.4.2
  • V10.4.5
  • V15.1.3
  • V15.4.1

Mitigating Controls (NIST 800-53 r5) AI

SC-39 Process Isolation partial match

Maintaining separate execution domains for each process structurally eliminates unintended concurrent access to the same shared resources.

SC-4 Information in Shared System Resources partial match

Preventing unintended information transfer through shared system resources directly addresses the improper concurrent modification that defines a race condition.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require proper synchronization primitives and concurrency testing that prevent race conditions.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect race conditions, but does not prevent them at design or coding time.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates concurrency controls and synchronization primitives that directly prevent race conditions.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify thread-safety and locking rules, but do not prescribe implementation details.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles require proper synchronization and resource isolation, addressing the root cause of CWE-362.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly forbid unsafe concurrent access patterns and mandate atomic operations or locks.

A.8.32 Change management none match
none

Change management reduces introduction of concurrency bugs during updates, yet does not address the weakness itself.

References