# CVE-2017-7436: libzypp accepts unsigned packages even when configured to check signatures

> Attackers can inject malicious RPM packages by bypassing signature checks in libzypp, leading to potential code execution on SUSE systems.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/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:** 1 Mar 2018
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2017-7436, GHSA-wf75-8v2m-5h2m, SUSE-SU-2017:2344-1, UBUNTU-CVE-2017-7436

## What is CVE-2017-7436?

CVE-2017-7436 is a high-severity vulnerability in SUSE libzypp, published on 1 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In libzypp before 20170803 it was possible to retrieve unsigned packages without a warning to the user which could lead to man in the middle or malicious servers to inject malicious RPM packages into a users system.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2017-7436?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libzypp` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 16.15.6-2.8.1 |
| `zypper` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 1.13.32-21.3.2 |
| `libzypp` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 16.15.6-2.8.1 |
| `zypper` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 1.13.32-21.3.2 |
| `libzypp` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 16.15.6-2.8.1 |
| `zypper` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 1.13.32-21.3.2 |
| `libzypp` | SUSE:Linux Enterprise Software Development Kit 12 SP3 | All versions | 16.15.6-2.8.1 |

Products: Opensuse Libzypp.

## How do I fix CVE-2017-7436?

Apply the vendor's patch.

## Is CVE-2017-7436 being exploited?

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

## Other vulnerabilities in SUSE libzypp

- [CVE-2026-25707](https://insights.sbomify.com/CVE-2026-25707/): Handcrafted repo metadata may cause arbitrary local files to be overwritten by libzypp (high 8.8)
- [CVE-2026-44941](https://insights.sbomify.com/CVE-2026-44941/): libzypp path traversal via "keyhint" in repomd.xml (high 8.4)
- [CVE-2017-7435](https://insights.sbomify.com/CVE-2017-7435/): libzypp accepts unsigned 3rd party repo without warning (high 8.1)
- [CVE-2018-7685](https://insights.sbomify.com/CVE-2018-7685/): libzypp does not reevaluate malicious rpms once downloaded (high 7.8)
- [CVE-2017-9269](https://insights.sbomify.com/CVE-2017-9269/): lack of keypinning in libzypp could lead to repository switching (high 7.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-7436 and fix it if it is affected.

What it is: CVE-2017-7436 is a high-severity vulnerability in SUSE libzypp, published on 1 Mar 2018. 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-2017-7436 in the wild and no public exploit code.

Affected product: SUSE libzypp. 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-2017-7436/ (Markdown: https://insights.sbomify.com/CVE-2017-7436/index.md)
```

## Sources

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

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