# OSV-2022-377: Heap-buffer-overflow in decode_preR13_section_hdr

> A heap buffer overflow in the DWG decoder allows attackers to execute arbitrary code or cause denial of service via malicious files.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Apr 2022

## What is OSV-2022-377?

OSV-2022-377 is a memory corruption vulnerability in libredwg, published on 26 Apr 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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

```
Crash type: Heap-buffer-overflow WRITE 4
Crash state:
decode_preR13_section_hdr
decode_preR13
dwg_decode
```

## Which versions are affected by OSV-2022-377?

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-2022-377?

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

## Is OSV-2022-377 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for OSV-2022-377 and fix it if it is affected.

What it is: OSV-2022-377 is a memory corruption vulnerability in libredwg, published on 26 Apr 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of OSV-2022-377 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-2022-377/ (Markdown: https://insights.sbomify.com/OSV-2022-377/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/OSV-2022-377

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