# GHSA-2xv3-h762-ccxv: Out-of-bounds Read in concat-with-sourcemaps

> An out-of-bounds read in concat-with-sourcemaps allows attackers to read uninitialized memory when a number is used as a separator.

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

## What is GHSA-2xv3-h762-ccxv?

GHSA-2xv3-h762-ccxv is a vulnerability in concat-with-sourcemaps, published on 29 May 2019. 

### Official description

Versions of `concat-with-sourcemaps` before 1.0.6 allocates uninitialized Buffers when a number is passed as a separator.

## Recommendation

Update to version 1.0.6 or later.

## Which versions are affected by GHSA-2xv3-h762-ccxv?

2 open source packages ship an affected version, including concat-with-sourcemaps.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `concat-with-sourcemaps` | npm | From 1.0.0 | 1.0.6 |
| `concat-with-sourcemaps` | npm | From 1.0.0 | 1.0.6 |

## How do I fix GHSA-2xv3-h762-ccxv?

Upgrade concat-with-sourcemaps to 1.0.6 or later.

## Is GHSA-2xv3-h762-ccxv being exploited?

There is no known exploitation of GHSA-2xv3-h762-ccxv in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-2xv3-h762-ccxv and fix it if it is affected.

What it is: GHSA-2xv3-h762-ccxv is a vulnerability in concat-with-sourcemaps, published on 29 May 2019. 
Exploitation: There is no known exploitation of GHSA-2xv3-h762-ccxv in the wild and no public exploit code.

Affected packages and fixed versions:
- concat-with-sourcemaps (npm): affected from 1.0.0; fixed in 1.0.6
- concat-with-sourcemaps (npm): affected from 1.0.0; fixed in 1.0.6

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-2xv3-h762-ccxv/ (Markdown: https://insights.sbomify.com/GHSA-2xv3-h762-ccxv/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-2xv3-h762-ccxv

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