# CVE-2017-14748: Race condition in n/a

> Remote authenticated users can cause denial of service for other players by exploiting a race condition when leaving a competitive match during loading.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-2jmv-57qj-jwg6

## What is CVE-2017-14748?

CVE-2017-14748 is a medium-severity vulnerability in n/a, published on 26 Sep 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Race condition in Blizzard Overwatch 1.15.0.2 allows remote authenticated users to cause a denial of service (season bans and SR losses for other users) by leaving a competitive match at a specific time during the initial loading of that match.

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

## Which versions are affected by CVE-2017-14748?

It affects 1 product.


Products: Blizzard Overwatch.

## How do I fix CVE-2017-14748?

No fix has been published for CVE-2017-14748 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-14748 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-14748 and fix it if it is affected.

What it is: CVE-2017-14748 is a medium-severity vulnerability in n/a, published on 26 Sep 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-14748 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2017-14748/ (Markdown: https://insights.sbomify.com/CVE-2017-14748/index.md)
```

## Sources

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

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