dbcve.org
StarstudioApplication · Lenovo

CVE-2024-9046

HIGH · 7.8 CVSS v3.1 Published 2024-10-11
Fix available
A fix is available. Upgrade to 2020.3.12.34806 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 stARstudio 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 · moderate confidence

A DLL hijacking vulnerability in Lenovo stARstudio allows a local attacker to place a malicious DLL in a location where the application loads DLLs from, achieving code execution with elevated privileges. This is a local privilege escalation issue requiring the attacker to have some level of access to the system to plant the malicious DLL.

MitigationApply the vendor patch or update Lenovo stARstudio to the latest version. Until patched, restrict write access to application directories and monitor for suspicious DLL files.

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
StarstudioApplication
Affected:< 2020.3.12.34806

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. Verify Lenovo stARstudio is installed
    Look for stARstudio application on the system - check Program Files directories, Start Menu, or search for stARstudio.exe using file explorer search or Get-ChildItem cmdlet
    Affected if The application is present on the system
  2. Locate the installed version
    Right-click on the stARstudio executable, select Properties, and view the Details tab for version information. Alternatively, use PowerShell: Get-Item 'C:\Program Files\*\stARstudio.exe' | Select-Object VersionInfo
    Affected if Version information cannot be retrieved or shows an older build
  3. Compare version to affected range
    Compare the installed version number to 2020.3.12.34806 - any version below this threshold is vulnerable
    Affected if Installed version is less than 2020.3.12.34806
  4. Check application directory permissions
    Right-click the stARstudio installation folder, go to Properties > Security, and verify which users have Write or Modify permissions to the directory
    Affected if Non-admin users have Write access to the application directory, making DLL planting possible
  5. Inspect for unauthorized DLLs
    Review all DLL files in the stARstudio installation directory for any unexpected or recently added files that do not match the legitimate application DLLs
    Affected if Unexpected DLL files are present in the application directory

The system is affected if Lenovo stARstudio is installed with a version lower than 2020.3.12.34806 and the application directory is writable by low-privilege users.

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 2020.3.12.34806 or later
Fixed in 2020.3.12.34806
Interim mitigation

Apply the vendor patch or update Lenovo stARstudio to the latest version. Until patched, restrict write access to application directories and monitor for suspicious DLL files.

Recommended fix Moderate confidence

2020.3.12.34806 or later

  1. 1. Navigate to the official Lenovo support website or iknow.lenovo.com.cn to download the fixed version
  2. 2. Uninstall the current version of Lenovo stARstudio from the system
  3. 3. Download stARstudio version 2020.3.12.34806 or later from Lenovo's official source
  4. 4. Install the updated stARstudio version following the on-screen prompts
  5. 5. Restart the system to ensure all components are properly loaded
  6. 6. Verify the installed version matches the fixed release (2020.3.12.34806 or higher)

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

Fix this in Starstudio Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-9046 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