# OSV-2023-758: Heap-double-free in bit_TV_to_utf8

> A heap double-free vulnerability in the JSON parsing library allows attackers to cause denial of service or potentially execute arbitrary code.

- **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:** 29 Aug 2023

## What is OSV-2023-758?

OSV-2023-758 is an use after free vulnerability in libredwg, published on 29 Aug 2023. 

### Official description

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

```
Crash type: Heap-double-free
Crash state:
bit_TV_to_utf8
json_cquote
json_header_write_private
```

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

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


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

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

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

## Is OSV-2023-758 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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