# OSV-2022-969: Heap-buffer-overflow in SkPath::Iter::next

> A heap-buffer-overflow in Skia's path iteration allows attackers to cause crashes or potentially execute code via crafted graphics data.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Sep 2022

## What is OSV-2022-969?

OSV-2022-969 is a memory corruption vulnerability in skia, published on 28 Sep 2022. An attacker can exploit it over the internet without logging in, 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=51875

```
Crash type: Heap-buffer-overflow READ 8
Crash state:
SkPath::Iter::next
SkRegion::setPath
SkRasterClip::SkRasterClip
```

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

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


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

## How do I fix OSV-2022-969?

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

## Is OSV-2022-969 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: OSV-2022-969 is a memory corruption vulnerability in skia, published on 28 Sep 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of OSV-2022-969 in the wild and no public exploit code.

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

## Sources

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

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