Use‑After‑Free in moxygen Data Stream Read Loop Causes Service Crash
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Meta Platforms, Inc | moxygen | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Meta Platforms Inc | Moxygen |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.255% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Use‑After‑Free in moxygen Data Stream Read Loop Causes Service Crash |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-416 | |
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Meta Platforms Inc
Meta Platforms Inc moxygen |
|
| Vendors & Products |
Meta Platforms Inc
Meta Platforms Inc moxygen |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In moxygen before commit 004123dd24c3, MoQSession::dataStreamReadLoop keeps using a stream read handle after reading a FIN, which invalidates the handle under proxygen's WebTransport API. A remote peer can trigger the stale use by opening a data stream that names an unknown track alias and carries the FIN in the same write. | |
| References |
|