# OSV-2023-862: Heap-use-after-free in g_datalist_get_flags

> A heap-use-after-free vulnerability in GStreamer's g_datalist_get_flags allows attackers to potentially execute code or cause denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2023

## What is OSV-2023-862?

OSV-2023-862 is an use after free vulnerability in gstreamer, published on 16 Sep 2023. 

### Official description

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=62381

```
Crash type: Heap-use-after-free READ 8
Crash state:
g_datalist_get_flags
g_object_unref
gst_object_unref
```

## Which versions are affected by OSV-2023-862?

1 open source package ship an affected version, including gstreamer.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gstreamer` | OSS-Fuzz | All versions | None |

## How do I fix OSV-2023-862?

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

## Is OSV-2023-862 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for OSV-2023-862 and fix it if it is affected.

What it is: OSV-2023-862 is an use after free vulnerability in gstreamer, published on 16 Sep 2023. 
Exploitation: There is no known exploitation of OSV-2023-862 in the wild and no public exploit code.

Affected packages and fixed versions:
- gstreamer (OSS-Fuzz): affected all versions; no fix listed

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/OSV-2023-862/ (Markdown: https://insights.sbomify.com/OSV-2023-862/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/OSV-2023-862

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