# OSV-2018-2: Heap-buffer-overflow in git_buf_vprintf

> A heap-buffer-overflow in the Git library's git_buf_vprintf function can lead to crashes or potential code execution.

- **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:** 12 Jan 2021

## What is OSV-2018-2?

OSV-2018-2 is a memory corruption vulnerability in libgit2, published on 12 Jan 2021. 

### Official description

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

```
Crash type: Heap-buffer-overflow READ 13
Crash state:
git_buf_vprintf
giterr_set
git__strntol32
```

## Which versions are affected by OSV-2018-2?

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


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

## How do I fix OSV-2018-2?

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

## Is OSV-2018-2 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for OSV-2018-2 and fix it if it is affected.

What it is: OSV-2018-2 is a memory corruption vulnerability in libgit2, published on 12 Jan 2021. 
Exploitation: There is no known exploitation of OSV-2018-2 in the wild and no public exploit code.

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

## Sources

- OSV: https://osv.dev/vulnerability/OSV-2018-2

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