App StoreApplication · Lenovo

CVE-2024-4130

HIGH · 7.8 CVSS v3.1 Published 2024-10-11
Fix available
A fix is available. Upgrade to 9.0.17 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A DLL hijack vulnerability was reported in Lenovo App Store that could allow a local attacker to execute code with elevated privileges.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A DLL hijacking vulnerability exists in Lenovo App Store where the application insecurely loads DLL files from locations writable by lower-privileged users. A local attacker can place a malicious DLL in these locations, causing the App Store (running with elevated privileges) to load and execute the attacker's code with those elevated privileges.

MitigationApply the Lenovo security patch when available. Until patched, remove or restrict access to Lenovo App Store, and monitor for unauthorized DLL placement in application directories.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
App StoreApplication
Affected:< 9.0.17

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Lenovo App Store installation
    Check for Lenovo App Store in program files (typically C:\Program Files\Lenovo\Lenovo App Store or C:\Program Files (x86)\Lenovo\Lenovo App Store), or look for the application in Add/Remove Programs
    Affected if Lenovo App Store is installed on the system
  2. Determine installed version
    Right-click the Lenovo App Store executable, select Properties, then check the Details tab for the version number. Alternatively, open Add/Remove Programs, find Lenovo App Store, and note the version shown
    Affected if The installed version is lower than 9.0.17 (for example, 9.0.0 through 9.0.16)
  3. Check directory permissions on App Store folder
    Right-click the Lenovo App Store installation folder, select Properties, go to the Security tab, and examine which users have Write or Modify permissions. Use icacls command (e.g., icacls "C:\Program Files\Lenovo\Lenovo App Store") to list explicit permissions
    Affected if Users without administrative privileges have Write or Modify access to the application directory
  4. Inspect for unexpected DLL files
    List all DLL files in the Lenovo App Store installation directory. Compare against expected DLLs by noting file creation dates and checking for unusually named or recently created DLLs that do not belong to the application
    Affected if A DLL file exists in the application directory that was created or modified by a non-administrative user, or any unexplained DLL is present

A user is affected if Lenovo App Store version is below 9.0.17 AND the application directory is writable by standard users, or if suspicious DLLs are present in the installation folder.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.0.17 or later
Fixed in 9.0.17
Interim mitigation

Apply the Lenovo security patch when available. Until patched, remove or restrict access to Lenovo App Store, and monitor for unauthorized DLL placement in application directories.

Recommended fix High confidence

9.0.17

  1. Navigate to the official Lenovo support or Lenovo App Store download page
  2. Download and install Lenovo App Store version 9.0.17 or later
  3. Verify the installed version matches or exceeds 9.0.17

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in App Store Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-4130 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-4130 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data