# CVE-2019-11371: Memory corruption in n/a

> A buffer overflow in BWA allows attackers to execute arbitrary code or cause denial of service via a crafted long prefix.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-11371, GHSA-476x-vw5v-gv5j, UBUNTU-CVE-2019-11371

## What is CVE-2019-11371?

CVE-2019-11371 is a critical memory corruption vulnerability in n/a, published on 20 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

BWA (aka Burrow-Wheeler Aligner) 0.7.17 r1198 has a Buffer Overflow via a long prefix that is mishandled in bns_fasta2bntseq and bns_dump at btnseq.c.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2019-11371?

It affects 1 product.


Products: Burrow-Wheeler Aligner Project Burrow-Wheeler Aligner.

## How do I fix CVE-2019-11371?

No fix has been published for CVE-2019-11371 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-11371 being exploited?

There is no known exploitation of CVE-2019-11371 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2019-10269](https://insights.sbomify.com/CVE-2019-10269/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-11371 and fix it if it is affected.

What it is: CVE-2019-11371 is a critical memory corruption vulnerability in n/a, published on 20 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-11371 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/CVE-2019-11371/ (Markdown: https://insights.sbomify.com/CVE-2019-11371/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-11371
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-11371
- OSV: https://osv.dev/vulnerability/CVE-2019-11371

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