# OSV-2024-1391: Heap-buffer-overflow in gsicc_create_getv2buffer

> A heap-buffer-overflow in Ghostscript's ICC color space handling allows attackers to cause crashes or potentially execute code via malicious PDFs.

- **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:** 20 Dec 2024

## What is OSV-2024-1391?

OSV-2024-1391 is a memory corruption vulnerability in ghostscript, published on 20 Dec 2024. 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=384972943

```
Crash type: Heap-buffer-overflow READ 12
Crash state:
gsicc_create_getv2buffer
pdf_iccbased_color_space
pdf_color_space_named
```

## Which versions are affected by OSV-2024-1391?

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


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

## How do I fix OSV-2024-1391?

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

## Is OSV-2024-1391 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for OSV-2024-1391 and fix it if it is affected.

What it is: OSV-2024-1391 is a memory corruption vulnerability in ghostscript, published on 20 Dec 2024. 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-2024-1391 in the wild and no public exploit code.

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

## Sources

- OSV: https://osv.dev/vulnerability/OSV-2024-1391

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