# OSV-2022-1157: Stack-buffer-overflow in merge_utf16be_ascii

> A stack buffer overflow in merge_utf16be_ascii allows attackers to cause denial of service or potentially execute code via crafted input.

- **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:** 10 Nov 2022

## What is OSV-2022-1157?

OSV-2022-1157 is a memory corruption vulnerability in util-linux, published on 10 Nov 2022. 

### Official description

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

```
Crash type: Stack-buffer-overflow WRITE 1
Crash state:
merge_utf16be_ascii
probe_isoNUMBER
superblocks_probe
```

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

1 open source package ship an affected version, including util-linux.


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

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

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

## Is OSV-2022-1157 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: OSV-2022-1157 is a memory corruption vulnerability in util-linux, published on 10 Nov 2022. 
Exploitation: There is no known exploitation of OSV-2022-1157 in the wild and no public exploit code.

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

## Sources

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

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