Arbitrary code execution via signature-check bypass
Published Mar 27, 2020 · Updated Aug 6, 2024
Improper signature verification in Lenovo System Update 5.07.0008 and earlier allows remote attackers to replace trusted updates. The available CVE and Lenovo records do not disclose the exact validation error that lets a modified update pass the signature check. No privileges or user interaction are required, and successful exploitation compromises update integrity and can lead to arbitrary code execution.
Summary
What happened
Improper signature verification in Lenovo System Update 5.07.0008 and earlier allows remote attackers to replace trusted updates. The available CVE and Lenovo records do not disclose the exact validation error that lets a modified update pass the signature check. No privileges or user interaction are required, and successful exploitation compromises update integrity and can lead to arbitrary code execution.
The record
- CVE
- CVE-2015-7336
- Published
- Mar 27, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-347, T1195.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 27, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Weakness, pattern, technique
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