# CVE-2016-1925: Integer overflow in n/a

> Remote attackers can trigger a buffer overflow via integer underflow in lha archives, potentially leading to code execution or denial of service.

- **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:** Yes
- **Published:** 23 Jan 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-c9qr-jrpq-4qqr, MGASA-2016-0142, SUSE-SU-2016:1904-1

## What is CVE-2016-1925?

CVE-2016-1925 is a critical vulnerability in n/a, published on 23 Jan 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Integer underflow in header.c in lha allows remote attackers to have unspecified impact via a large header size value for the (1) level0 or (2) level1 header in a lha archive, which triggers a buffer overflow.

Weakness: CWE-191 (Integer Underflow (Wrap or Wraparound))

## Which versions are affected by CVE-2016-1925?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `lha` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 1.14.0.894-3.1 |
| `lha` | SUSE:Linux Enterprise Server for SAP Applications 11 SP4 | All versions | 1.14.0.894-3.1 |

Products: Lha for Unix Project Lha for Unix.

## How do I fix CVE-2016-1925?

Apply the vendor's patch.

## Is CVE-2016-1925 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-1925 and fix it if it is affected.

What it is: CVE-2016-1925 is a critical vulnerability in n/a, published on 23 Jan 2017. 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-2016-1925 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-2016-1925/ (Markdown: https://insights.sbomify.com/CVE-2016-1925/index.md)
```

## Sources

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

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