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

> A heap-based buffer over-read in libfwsi allows attackers to cause denial of service or disclose sensitive memory contents via crafted input.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2019
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-17263, GHSA-wpqw-8rxf-9cw7

## What is CVE-2019-17263?

CVE-2019-17263 is a low-severity memory corruption vulnerability in n/a, published on 6 Oct 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In libyal libfwsi before 20191006, libfwsi_extension_block_copy_from_byte_stream in libfwsi_extension_block.c has a heap-based buffer over-read because rejection of an unsupported size only considers values less than 6, even though values of 6 and 7 are also unsupported. NOTE: the vendor has disputed this as described in the GitHub issue

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Libfwsi Project Libfwsi.

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

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

## Is CVE-2019-17263 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-17263 is a low-severity memory corruption vulnerability in n/a, published on 6 Oct 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-17263 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-17263/ (Markdown: https://insights.sbomify.com/CVE-2019-17263/index.md)
```

## Sources

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

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