Package modification via improper repository certificate validation
Published Jan 27, 2020 · Updated Sep 16, 2024
Improper certificate validation in SUSE Studio Onsite 1.3.17-56.6.3 and earlier allows remote attackers to modify retrieved packages. The susestudio-common component fails to validate certificates correctly when connecting to software repositories, allowing a man-in-the-middle endpoint to supply altered repository metadata and packages. Exploitation requires control of a position capable of intercepting repository traffic; the bounded result is modification of content received over those connections.
Summary
What happened
Improper certificate validation in SUSE Studio Onsite 1.3.17-56.6.3 and earlier allows remote attackers to modify retrieved packages. The susestudio-common component fails to validate certificates correctly when connecting to software repositories, allowing a man-in-the-middle endpoint to supply altered repository metadata and packages. Exploitation requires control of a position capable of intercepting repository traffic; the bounded result is modification of content received over those connections.
The record
- CVE
- CVE-2017-14806
- Published
- Jan 27, 2020
- Updated
- Sep 16, 2024
- Vendor
- SUSE
- Product
- SUSE Studio Onsite
- Classifications
- CWE-295, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 27, 2020CVE publishedPublication date reported by the CVE source.
- Sep 16, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=susestudio-common <=1.3.17-56.6.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo