# OSV-2023-675: Heap-use-after-free in parse_options

> A heap-use-after-free vulnerability in parse_options allows attackers to potentially execute arbitrary code or cause denial of service.

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

## What is OSV-2023-675?

OSV-2023-675 is an use after free vulnerability in flac, published on 9 Aug 2023. 

### Official description

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

```
Crash type: Heap-use-after-free WRITE 4
Crash state:
parse_options
append_new_operation
parse_options
```

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

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


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

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

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

## Is OSV-2023-675 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: OSV-2023-675 is an use after free vulnerability in flac, published on 9 Aug 2023. 
Exploitation: There is no known exploitation of OSV-2023-675 in the wild and no public exploit code.

Affected packages and fixed versions:
- flac (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-675/ (Markdown: https://insights.sbomify.com/OSV-2023-675/index.md)
```

## Sources

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

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