# CVE-2020-19497: Integer overflow in n/a

> An integer overflow in the MAT File I/O Library allows attackers to cause a denial of service via crafted input.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 21 Jul 2021
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2020-19497, GHSA-6wj5-q7pj-g748, UBUNTU-CVE-2020-19497

## What is CVE-2020-19497?

CVE-2020-19497 is a high-severity vulnerability in n/a, published on 21 Jul 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Integer overflow vulnerability in Mat_VarReadNextInfo5 in mat5.c in tbeu matio (aka MAT File I/O Library) 1.5.17, allows attackers to cause a Denial of Service or possibly other unspecified impacts.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2020-19497?

It affects 1 product.


Products: Matio Project Matio.

## How do I fix CVE-2020-19497?

Upgrade to a fixed version.

## Is CVE-2020-19497 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-9028](https://insights.sbomify.com/CVE-2019-9028/): Memory corruption in n/a (critical 9.1)
- [CVE-2019-9030](https://insights.sbomify.com/CVE-2019-9030/): Memory corruption in n/a (critical 9.1)
- [CVE-2019-9033](https://insights.sbomify.com/CVE-2019-9033/): Memory corruption in n/a (critical 9.1)
- [CVE-2019-9034](https://insights.sbomify.com/CVE-2019-9034/): Memory corruption in n/a (critical 9.1)
- [CVE-2019-9035](https://insights.sbomify.com/CVE-2019-9035/): Memory corruption in n/a (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-19497 and fix it if it is affected.

What it is: CVE-2020-19497 is a high-severity vulnerability in n/a, published on 21 Jul 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-19497 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-2020-19497/ (Markdown: https://insights.sbomify.com/CVE-2020-19497/index.md)
```

## Sources

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

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