# CVE-2023-50923: Information disclosure in n/a

> Remote attackers can establish a covert channel by manipulating the Latency Spin Bit in QUIC, potentially leaking sensitive information.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/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:** No
- **Published:** 20 Feb 2024
- **Updated:** 4 Dec 2024
- **Also known as:** GHSA-48f4-cx87-w7mh

## What is CVE-2023-50923?

CVE-2023-50923 is a medium-severity vulnerability in n/a, published on 20 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In QUIC in RFC 9000, the Latency Spin Bit specification (section 17.4) does not strictly constrain the bit value when the feature is disabled, which might allow remote attackers to construct a covert channel with data represented as changes to the bit value. NOTE: The "Sheridan, S., Keane, A. (2015). In Proceedings of the 14th European Conference on Cyber Warfare and Security (ECCWS), University of Hertfordshire, Hatfield, UK." paper says "Modern Internet communication protocols provide an almost infinite number of ways in which data can be hidden or embed whithin seemingly normal network traffic."

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2023-50923 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-50923 is a medium-severity vulnerability in n/a, published on 20 Feb 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-50923 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-2023-50923/ (Markdown: https://insights.sbomify.com/CVE-2023-50923/index.md)
```

## Sources

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

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