Lenovo Group Ltd. vulnerabilities, page 2
65 vulnerabilities
Known vulnerabilities in Lenovo Group Ltd. products, newest first, with CVSS severity, EPSS, KEV listings and ransomware use, across 46 products.
CVE-2016-8226lenovo group ltd.system x m5, m6, and x6 bios+11
EPSS score0.92%
The BIOS in Lenovo System X M5, M6, and X6 systems allows administrators to cause a denial of service via updating a UEFI data structure.CVE-2016-8221lenovo group ltd.xclarity administrator (lxca)+1EPSS score0.30%
Privilege Escalation in Lenovo XClarity Administrator earlier than 1.2.0, if LXCA is used to manage rack switches or chassis with embedded input/output modules (IOMs), certain log files viewable by authenticated users may contain passwords for internal administrative LXCA accounts with temporary passwords that are used internally by LXCA code.CVE-2016-8233lenovo group ltd.xclarity administrator+1EPSS score1.14%
Log files generated by Lenovo XClarity Administrator (LXCA) versions earlier than 1.2.2 may contain user credentials in a non-secure, clear text form that could be viewed by a non-privileged user.CVE-2016-8225lenovo group ltd.edge and slim usb keyboard driver+2EPSS score0.35%
Unquoted service path vulnerability in Lenovo Edge and Lenovo Slim USB Keyboard Driver versions earlier than 1.21 allows local users to execute code with elevated privileges.CVE-2016-8228lenovo group ltd.service bridge+1EPSS score0.37%
In Lenovo Service Bridge before version 4, a user with local privileges on a system could execute code with administrative privileges.CVE-2016-8227lenovo group ltd.transition application+1EPSS score0.35%
Privilege escalation vulnerability in Lenovo Transition application used in Lenovo Yoga, Flex and Miix systems running Windows allows local users to execute code with elevated privileges.CVE-2016-8236lenovo group ltd.thinkserver rd350, rd450, rd550, rd650, td350+1EPSS score0.82%
Reset to default settings may occur in Lenovo ThinkServer TSM RD350, RD450, RD550, RD650, TD350 during a prolonged broadcast storm in TSM versions earlier than 3.77.CVE-2016-8237lenovo group ltd.lenovo updates+1EPSS score3.34%
Remote code execution in Lenovo Updates (not Lenovo System Update) allows man-in-the-middle attackers to execute arbitrary code.CVE-2016-8231lenovo group ltd.service bridge+1EPSS score0.51%
In Lenovo Service Bridge before version 4, a bug found in the signature verification logic of the code signing certificate could be exploited by an attacker to insert a forged code signing certificate.CVE-2016-8230lenovo group ltd.service bridge+1EPSS score1.09%
In Lenovo Service Bridge before version 4, an insecure HTTP connection is used by LSB to send system serial number, machine type and model and product name to Lenovo's servers.CVE-2016-8222lenovo group ltd.thinkpad systems+74EPSS score0.30%
A vulnerability has been identified in a signed kernel driver for the BIOS of some ThinkPad systems that can allow an attacker with Windows administrator-level privileges to call System Management Mode (SMM) services. This could lead to a denial of service attack or allow certain BIOS variables or settings to be altered (such as boot sequence). The setting or changing of BIOS passwords is not affected by this vulnerability.CVE-2016-8223lenovo group ltd.all thinkpad, thinkcentre, thinkstation and lenovo-branded systems preloaded with the windows 10 operating system, or any system running lenovo companion, lenovo settings, or lenovo id.+1EPSS score0.31%
During an internal security review, Lenovo identified a local privilege escalation vulnerability in Lenovo System Interface Foundation software installed on some Windows 10 PCs where a user with local privileges could run arbitrary code with administrator level privileges.CVE-2016-8235lenovo group ltd.customer care software development kit (ccsdk)+1EPSS score0.42%
Privilege escalation in Lenovo Customer Care Software Development Kit (CCSDK) versions earlier than 2.0.16.3 allows local users to execute code with elevated privileges.CVE-2017-3753lenovo group ltd.desktop and notebook bios+111EPSS score0.52%
A vulnerability has been identified in some Lenovo products that use UEFI (BIOS) code developed by American Megatrends, Inc. (AMI). With this vulnerability, conditions exist where an attacker with administrative privileges or physical access to a system may be able to run specially crafted code that can allow them to bypass system protections such as Device Guard and Hyper-V.CVE-2017-3748googleandroid+1EPSS score0.18%
On Lenovo VIBE mobile phones, improper access controls on the nac_server component can be abused in conjunction with CVE-2017-3749 and CVE-2017-3750 to elevate privileges to the root user (commonly known as 'rooting' or "jail breaking" a device).CVE-2017-3754lenovo group ltd.lenovo notebook bios+1EPSS score0.34%
Some Lenovo brand notebook systems do not have write protections properly configured in the system BIOS. This could enable an attacker with physical or administrative access to a system to be able to flash the BIOS with an arbitrary image and potentially run malicious BIOS code.CVE-2017-3746lenovo group ltd.thinkpad usb 3.0 ethernet adapter driver+1EPSS score0.38%
ThinkPad USB 3.0 Ethernet Adapter (part number 4X90E51405) driver, various versions, was found to contain a privilege escalation vulnerability that could allow a local user to execute arbitrary code with administrative or system level privileges.CVE-2017-3750googleandroid+1EPSS score0.14%
On Lenovo VIBE mobile phones, the Lenovo Security Android application allows private data to be backed up and restored via Android Debug Bridge, which allows tampering leading to privilege escalation in conjunction with CVE-2017-3748 and CVE-2017-3749.CVE-2017-3747lenovo group ltd.lenovo nerve center+1EPSS score0.29%
Privilege escalation vulnerability in Lenovo Nerve Center for Windows 10 on Desktop systems (Lenovo Nerve Center for notebook systems is not affected) that could allow an attacker with local privileges on a system to alter registry keys.CVE-2017-3763lenovo group ltd.lenovo xclarity administrator (lxca)+1EPSS score0.32%
An attacker who obtains access to the location where the LXCA file system is stored may be able to access credentials of local LXCA accounts in LXCA versions earlier than 1.3.2.