Skip to main content

Lenovo Baiying Client CVE-2025-13155

HIGH
Incorrect Default Permissions (CWE-276)
2025-12-10 psirt@lenovo.com
8.5
CVSS 4.0 · Vendor: lenovo
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain local low-privileged account on host
  2. Delivery
    Identify weak permissions on Baiying Client files/service
  3. Exploit
    Plant or modify executable in privileged path
  4. Execution
    Trigger privileged execution
  5. Impact
    Gain elevated code execution and full host compromise

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V13 - Configuration Default permission hardening
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Attacker must already be a local, authenticated user on a machine where the Lenovo Baiying Client is installed and running; exploitation leverages incorrect/weak permissions (CWE-276) on the client's files, directories, or service to escalate. Limiting factors: no remote vector (AV:L) so no network exploitation and no reachability from outside the host; the attacker needs an existing low-privilege account (PR:L); no user interaction is required (UI:N); impact is confined to the local system (no scope change, SC/SI/SA:N). Exposure is therefore restricted to hosts running this specific Lenovo product, predominantly in Lenovo-managed/China-market environments.

Impact

This is a genuine but not emergency-priority local privilege escalation. The CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:L/UI:N) indicates local access with low attack complexity and low privileges already required, yielding high confidentiality, integrity, and availability impact (VC:H/VI:H/VA:H) with no scope/subsequent-system change - consistent with CWE-276 (improper/incorrect permissions) letting an already-authenticated low-privileged user run code with elevated rights. The vendor-assigned base score is 8.5 (High), but the real-world urgency is tempered: EPSS is very low at 0.12% (2nd percentile), there is no CISA KEV listing, and no public exploit code was identified, so this reads as a credible-but-not-actively-exploited issue rather than a widespread threat. Crucially, exploitation is NOT remote - it requires an attacker to already be a local authenticated user on a host running the Lenovo Baiying Client, which materially limits the exploitable population to existing users/footholds. Signals are internally consistent (local vector matches the 'local authenticated user' description), so there is no CVSS-vs-description conflict to flag; the main missing data is independent confirmation of affected/fixed versions, as the sole reference is a Lenovo knowledge-base page with no scrapeable advisory metadata here.

Exploit ScenarioDerived

A low-privileged user who already has an account on a system running the Lenovo Baiying Client abuses weak file/directory or service permissions (CWE-276) to replace or inject a binary/script that the client executes at a higher privilege level, resulting in code execution with elevated (likely SYSTEM/admin) rights. No public exploit code was identified at time of analysis, and because the attack is local with low complexity, a motivated insider or an attacker who has already gained a basic foothold could reliably achieve full host compromise.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 14, 2026

Local privilege escalation in the Lenovo Baiying Client allows an authenticated low-privilege user to execute code with elevated privileges by abusing improperly secured files, directories, or service components of the client. Only hosts running this Lenovo client - predominantly Lenovo-managed and China-market environments - are exposed, since exploitation requires an existing account on the local machine and there is no network-reachable vector. Risk is currently low in the wider ecosystem: EPSS is 0.12% (2nd percentile), no public exploit code has been identified at time of analysis, and the issue is not listed as confirmed actively exploited (CISA KEV).

RemediationAI

No vendor-released patch identified at time of analysis; administrators should check the Lenovo advisory at https://iknow.lenovo.com.cn/detail/435005 for an updated client build or remediation tool and apply it once available, since that advisory is the only authoritative source for a fix version. Until then, the most targeted compensating control is to audit and harden filesystem and service ACLs on the client's installation directory, binaries, configuration files, and its Windows service definition, removing write/modify rights from non-administrative users and groups (Authenticated Users, Users, Everyone) so that a low-privilege account cannot substitute code or alter service parameters; the trade-off is that the client's self-update or per-user configuration may stop working and updates must then be applied by an administrator. Additionally, run the client's service under a dedicated least-privilege account rather than LocalSystem where the product permits, and restrict interactive logon rights on the affected hosts so that untrusted users cannot hold a local session at all - at the cost of reduced workstation-sharing flexibility. Monitoring for unexpected writes or process creation inside the client's install path can provide detection coverage in the interim, but none of these controls removes the underlying misconfiguration as reliably as the vendor fix.

Affected ProductsAI

The affected product is the Lenovo Baiying Client, a Lenovo endpoint client; the available input does not enumerate specific version ranges or CPE identifiers, so the precise affected builds must be confirmed against the vendor advisory at https://iknow.lenovo.com.cn/detail/435005 (Lenovo PSIRT, reporter psirt@lenovo.com). Exposure is limited to machines where the client is installed and running, which in practice means Lenovo-managed fleets, heavily skewed toward China-market deployments; hosts without this product are not affected.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-276 (Incorrect Default Permissions). Rather than a memory-safety or injection flaw, the defect is a configuration/ACL weakness: a component of the Lenovo Baiying Client - its install directory, an executable or DLL, a configuration file, or the service it installs - is shipped with permissions that grant non-administrative local users write or modify access. A low-privilege attacker can leverage that access to replace or alter code, configuration, or service definition such that it is later loaded or executed in an elevated context, achieving privilege escalation. The supplied CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N) and the independent assessment's CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) agree on the profile: local attack path only, low privileges required, no user interaction, high confidentiality/integrity/availability impact confined to the vulnerable host with no scope change and no subsequent-system impact. Because the vector specifies PR:L, exploitation requires an authenticated local user; because it specifies AV:L, there is no remote or cross-host reachability.

Know when Lenovo gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (lenovo) PRIMARY 8.5 HIGH
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
vuln.today AI 7.8 HIGH

Local vector and existing low-privilege account required (AV:L/PR:L), straightforward permission abuse (AC:L), no UI, full local compromise (C/I/A:H), no scope change.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (lenovo).

CVSS VectorVendor: lenovo

Attack Vector
Local
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

An improper permissions vulnerability was reported in Lenovo Baiying Client that could allow a local authenticated user to execute code with elevated privileges.

Executive ViewAI

Why It Matters

Lenovo Baiying Client contains a high-severity local privilege escalation issue that could allow someone with an existing local account to run code with elevated privileges on affected hosts. The exposure is concentrated in Lenovo-managed and China-market environments where this client is deployed, so leadership should prioritize visibility and containment for those endpoints. At time of analysis, no public exploit identified at time of analysis and no vendor-released patch identified at time of analysis, making interim controls and vendor monitoring the near-term priority.

Business Impact: Medium
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include restricting local interactive logon and removing unnecessary local accounts on hosts running Lenovo Baiying Client, reviewing and hardening permissions on client files, directories, and service components, enforcing least privilege and application allowlisting, enabling EDR monitoring for privilege escalation, and disabling or uninstalling the client where not required; monitor Lenovo's advisory for a patched version.

Threat Intelligence Overview

EPSS Score
0.1%
Top 98% exploitable
Prevalence
Low
Niche Lenovo client software, primarily China-market enterprise/endpoint deployment
Data Quality
3 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact
Medium

Priority Score

42
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +42
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

More in Lenovo

View all
CVE-2017-5638 CRITICAL POC
9.8 Mar 11

The Jakarta Multipart parser in Apache Struts 2 2.3.x before 2.3.32 and 2.5.x before 2.5.10.1 has incorrect exception ha

CVE-2012-1195 HIGH POC
7.5 Feb 18

Unrestricted file upload vulnerability in andesk/managementsuite/core/core.anonymous/ServerSetup.asmx in the ServerSetup

CVE-2012-1196 MEDIUM POC
5.0 Feb 18

Directory traversal vulnerability in the VulCore web service (WSVulnerabilityCore/VulCore.asmx) in Lenovo ThinkManagemen

CVE-2015-2219 HIGH POC
7.2 May 12

Lenovo System Update (formerly ThinkVantage System Update) before 5.06.0034 uses predictable security tokens, which allo

CVE-2018-14066 CRITICAL POC
9.8 Jul 15

The content://wappush content provider in com.android.provider.telephony, as found in some custom ROMs for Android phone

CVE-2026-58583 HIGH POC
8.4 Jul 07

Local privilege escalation in the FluxInk (formerly Sunia SPB Peripheral) Color Management Driver TcnPeripheral64.sys ve

CVE-2017-7293 HIGH POC
7.8 Apr 26

The Dolby DAX2 and DAX3 API services are vulnerable to a privilege escalation vulnerability that allows a normal user to

CVE-2015-6971 HIGH POC
7.8 Oct 03

Lenovo System Update (formerly ThinkVantage System Update) before 5.07.0013 allows local users to submit commands to the

CVE-2015-8110 HIGH POC
7.8 Apr 24

Lenovo System Update (formerly ThinkVantage System Update) before 5.07.0019 allows local users to gain privileges by nav

CVE-2021-3633 HIGH POC
7.8 Aug 17

A DLL preloading vulnerability was reported in Lenovo Driver Management prior to version 2.9.0719.1104 that could allow

CVE-2022-0354 HIGH POC
7.3 Apr 22

A vulnerability was reported in Lenovo System Update that could allow a local user with interactive system access the ab

CVE-2015-3214 MEDIUM POC
6.9 Aug 31

The pit_ioport_read in i8254.c in the Linux kernel before 2.6.33 and QEMU before 2.3.1 does not distinguish between read

References

Advisories & patches

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy