libzypp accepts unsigned packages even when configured to check signatures
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.
- Published
- Mar 1, 2018
- Updated
- Jun 16, 2026
- EPSS
- 1.8% · 78th percentile
- CWE
- CWE-20
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
33
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.8%
CNA vs NVD score
- NVD
- 8.1
- CNA · microfocus
- 8.1
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| opensuse | libzypp | cpe:2.3:a:opensuse:libzypp |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- opensuse libzyppup to 16.15.2 inclusive
Versions reported by the vendor
Affected version ranges reported by the assigning authority (microfocus). Independent of NVD's CPE analysis and usually ahead of it.
SUSE libzypp
- unspecified and later · before 20170803affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | libzypp | before 17.3.1-1 | 17.3.1-1 |
| openSUSE:Tumbleweed | zypper | before 1.14.49-1.2 | 1.14.49-1.2 |
| SUSE:Linux Enterprise Desktop 12 SP2 | libzypp | before 16.15.2-27.21.1 | 16.15.2-27.21.1 |
| SUSE:Linux Enterprise Desktop 12 SP2 | zypper | before 1.13.30-18.13.3 | 1.13.30-18.13.3 |
| SUSE:Linux Enterprise Desktop 12 SP3 | libzypp | before 16.15.6-2.8.1 | 16.15.6-2.8.1 |
| SUSE:Linux Enterprise Desktop 12 SP3 | libzypp | before 16.15.3-2.3.1 | 16.15.3-2.3.1 |
| SUSE:Linux Enterprise Desktop 12 SP3 | yast2-pkg-bindings | before 3.2.4-2.3.1 | 3.2.4-2.3.1 |
| SUSE:Linux Enterprise Desktop 12 SP3 | zypper | before 1.13.32-21.3.2 | 1.13.32-21.3.2 |
| SUSE:Linux Enterprise Server 12-LTSS | libzypp | before 14.45.17-2.82.1 | 14.45.17-2.82.1 |
| SUSE:Linux Enterprise Server 12-LTSS | zypper | before 1.11.70-2.69.2 | 1.11.70-2.69.2 |
| SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | libzypp | before 15.25.17-46.22.1 | 15.25.17-46.22.1 |
| SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | zypper | before 1.12.59-46.10.1 | 1.12.59-46.10.1 |
| SUSE:Linux Enterprise Software Development Kit 12 SP3 | yast2-pkg-bindings-devel-doc | before 3.2.4-2.3.1 | 3.2.4-2.3.1 |
Same product
opensuse: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-9269lack of keypinning in libzypp could lead to repository switching40Plan
- CVE-2026-44941libzypp path traversal via "keyhint" in repomd.xml35Monitor
- CVE-2026-25707Handcrafted repo metadata may cause arbitrary local files to be overwritten by libzypp35Monitor
- CVE-2017-7435libzypp accepts unsigned 3rd party repo without warning33Monitor
- CVE-2018-7685libzypp does not reevaluate malicious rpms once downloaded31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:libzypp | 17.3.1-1 · Debian:12 | Package registry (OSV) |
| opensuse:zypper | 1.14.49-1.2 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:libzypp | 16.15.2-27.21.1 · SUSE:Linux Enterprise Desktop 12 SP2 | Package registry (OSV) |
| suse:yast2-pkg-bindings | 3.2.4-2.3.1 · SUSE:Linux Enterprise Desktop 12 SP3 | Package registry (OSV) |
| suse:yast2-pkg-bindings-devel-doc | 3.2.4-2.3.1 · SUSE:Linux Enterprise Software Development Kit 12 SP3 | Package registry (OSV) |
| suse:zypper | 1.13.30-18.13.3 · SUSE:Linux Enterprise Desktop 12 SP2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-20 · Improper Input ValidationCVSS vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
ATT&CK techniques
- Obfuscated Files or InformationT1027
- Masquerading: Invalid Code SignatureT1036.001
- Steal Web Session CookieT1539
- Subvert Trust Controls: Code SigningT1553.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- www.suse.com/de-de/security/cve/CVE-2017-7436/
- bugzilla.suse.com/show_bug.cgi?id=1038984
- lists.opensuse.org/opensuse-security-announce/2017-08/msg00002.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.