# GHSA-xm7f-x4wx-wmgv: Out-of-bounds Read in byte

> An out-of-bounds read in the byte library allows attackers to read uninitialized memory, potentially causing crashes or data leaks.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 4 Jun 2019

## What is GHSA-xm7f-x4wx-wmgv?

GHSA-xm7f-x4wx-wmgv is a memory corruption vulnerability in byte, published on 4 Jun 2019. 

### Official description

Versions of `byte` before 1.4.1 allocate uninitialized buffers and read data from them past the initialized length

## Recommendation

Update to version 1.4.1 or later.

## Which versions are affected by GHSA-xm7f-x4wx-wmgv?

2 open source packages ship an affected version, including byte.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `byte` | npm | All versions | 1.4.1 |
| `byte` | npm | All versions | 1.4.1 |

## How do I fix GHSA-xm7f-x4wx-wmgv?

Upgrade byte to 1.4.1 or later.

## Is GHSA-xm7f-x4wx-wmgv being exploited?

There is no known exploitation of GHSA-xm7f-x4wx-wmgv in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-xm7f-x4wx-wmgv and fix it if it is affected.

What it is: GHSA-xm7f-x4wx-wmgv is a memory corruption vulnerability in byte, published on 4 Jun 2019. 
Exploitation: There is no known exploitation of GHSA-xm7f-x4wx-wmgv in the wild and no public exploit code.

Affected packages and fixed versions:
- byte (npm): affected all versions; fixed in 1.4.1
- byte (npm): affected all versions; fixed in 1.4.1

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/GHSA-xm7f-x4wx-wmgv/ (Markdown: https://insights.sbomify.com/GHSA-xm7f-x4wx-wmgv/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-xm7f-x4wx-wmgv

---
From sbomify Insights: https://insights.sbomify.com/GHSA-xm7f-x4wx-wmgv/
Summaries are generated and may contain mistakes; the official description above is the record.