# CVE-2023-49619: Apache Answer: Repeated submissions using scripts resulted in an abnormal number of collections for questions.

> Attackers can exploit a race condition to artificially inflate question bookmark counts via repeated script submissions.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jan 2024
- **Updated:** 11 Jun 2025
- **Also known as:** GHSA-f899-4mr4-fqpv, GO-2024-2457

## What is CVE-2023-49619?

CVE-2023-49619 is a low-severity vulnerability in Apache Answer, published on 10 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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 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.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2023-49619?

3 open source packages ship an affected version, including github.com/apache/incubator-answer. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/apache/incubator-answer` | Go | All versions | 1.2.1 |
| `github.com/apache/incubator-answer` | Go | All versions | 1.2.1 |
| `github.com/apache/incubator-answer` | Go | All versions | 1.2.1 |

Products: Apache Answer.

## How do I fix CVE-2023-49619?

Upgrade github.com/apache/incubator-answer to 1.2.1 or later.

## Is CVE-2023-49619 being exploited?

There is no known exploitation of CVE-2023-49619 in the wild and no public exploit code.

## Other vulnerabilities in Apache Answer

- [CVE-2026-60053](https://insights.sbomify.com/CVE-2026-60053/): Apache Answer: Residual Administrative API Key Access After Role or Account Revocation (critical 9.1)
- [CVE-2024-22393](https://insights.sbomify.com/CVE-2024-22393/): Apache Answer: Pixel Flood Attack by uploading the large pixel file (critical 9.1)
- [CVE-2026-48834](https://insights.sbomify.com/CVE-2026-48834/): Apache Answer: Denial of service via crafted Accept-Language header parsing (high 7.5)
- [CVE-2026-48911](https://insights.sbomify.com/CVE-2026-48911/): Apache Answer: Unauthenticated OAuth Email-Binding Account Takeover via Existing User Confirmation Flow (high 7.5)
- [CVE-2026-60023](https://insights.sbomify.com/CVE-2026-60023/): Apache Answer: Unauthorized disclosure of deleted or pending answer content (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-49619 and fix it if it is affected.

What it is: CVE-2023-49619 is a low-severity vulnerability in Apache Answer, published on 10 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-49619 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/apache/incubator-answer (Go): affected all versions; fixed in 1.2.1
- github.com/apache/incubator-answer (Go): affected all versions; fixed in 1.2.1
- github.com/apache/incubator-answer (Go): affected all versions; fixed in 1.2.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-49619/ (Markdown: https://insights.sbomify.com/CVE-2023-49619/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-49619
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-49619
- OSV: https://osv.dev/vulnerability/CVE-2023-49619

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-49619/
Summaries are generated and may contain mistakes; the official description above is the record.