# CVE-2018-10195: Integer overflow in n/a

> An integer overflow in lrzsz allows attackers to leak sensitive information to the receiving side during file transfers.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H`)
- **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:** Yes
- **Published:** 2 Jun 2021
- **Updated:** 5 Aug 2024
- **Also known as:** AZL-36960, AZL-7285, DEBIAN-CVE-2018-10195, DLA-2900-1, GHSA-54q2-pv96-8qc2, MGASA-2022-0049, SUSE-SU-2018:1066-1, SUSE-SU-2018:1070-1, UBUNTU-CVE-2018-10195, openSUSE-SU-2024:11363-1

## What is CVE-2018-10195?

CVE-2018-10195 is a high-severity vulnerability in Debian Debian Linux, published on 2 Jun 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

lrzsz before version 0.12.21~rc can leak information to the receiving side due to an incorrect length check in the function zsdata that causes a size_t to wrap around.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2018-10195?

It affects 5 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rzsz` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 0.12.21~rc-1001.3.1 |
| `rzsz` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 0.12.21~rc-936.3.1 |
| `rzsz` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 0.12.21~rc-1001.3.1 |
| `rzsz` | SUSE:Linux Enterprise Server for SAP Applications 11 SP4 | All versions | 0.12.21~rc-936.3.1 |
| `rzsz` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 0.12.21~rc-1001.3.1 |
| `rzsz` | openSUSE:Tumbleweed | All versions | 0.12.21~rc-4.5 |

Products: Debian Debian Linux, Lrzsz Project Lrzsz, Suse Linux Enterprise Debuginfo, Suse Linux Enterprise Desktop, Suse Linux Enterprise Server.

## How do I fix CVE-2018-10195?

Upgrade to a fixed version.

## Is CVE-2018-10195 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-10195 and fix it if it is affected.

What it is: CVE-2018-10195 is a high-severity vulnerability in Debian Debian Linux, published on 2 Jun 2021. 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-2018-10195 in the wild and no public exploit code.

Affected product: Debian Debian Linux. 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-2018-10195/ (Markdown: https://insights.sbomify.com/CVE-2018-10195/index.md)
```

## Sources

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

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