dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2024-2175

HIGH · 7.8 CVSS v3.1 Published 2024-08-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
An insecure permissions vulnerability was reported in Lenovo Display Control Center (LDCC) and Lenovo Accessories and Display Manager (LADM) that could allow a local attacker to escalate 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 local privilege escalation vulnerability exists in Lenovo Display Control Center (LDCC) and Lenovo Accessories and Display Manager (LADM) due to insecure file or service permissions. A local attacker with limited access could manipulate improperly secured files, directories, or service configurations to gain elevated (administrator/system) privileges.

MitigationApply vendor-provided security patches for LDCC and LADM, or update to patched versions. Alternatively, restrict permissions on affected application directories and services to authenticated users only, removing write access for low-privilege accounts.

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

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 LDCC or LADM installation
    Open Programs and Features (Windows) or check common installation paths like C:\Program Files\Lenovo\ or C:\Program Files (x86)\Lenovo\ for Lenovo Display Control Center or Lenovo Accessories and Display Manager. Use command: Get-ItemProperty 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Lenovo*Display*Control*' -or $_.DisplayName -like '*Lenovo*Accessories*Display*Manager*'}
    Affected if Either Lenovo Display Control Center or Lenovo Accessories and Display Manager appears in installed programs list
  2. Inspect LDCC/LADM directory permissions
    Right-click the installation folder (typically under C:\Program Files\Lenovo\), select Properties > Security, and verify that users other than Administrators or SYSTEM have Write or Modify permissions. From command line: icacls 'C:\Program Files\Lenovo\<application_folder>'
    Affected if Non-admin users or the Users group have Write, Modify, or Full Control permissions on the application directory
  3. Check Windows service configuration for LDCC/LADM services
    Run services.msc and look for Lenovo-related display or accessory services. Right-click each service, go to Properties, and verify the account under which the service runs. Also check: sc qc <service_name>
    Affected if The service runs under SYSTEM or Administrator account AND low-privilege users have Write permissions on the service executable or its directory
  4. Examine executable file permissions
    Use icacls on the main executable files in the Lenovo application directory (typically .exe files in the installation folder) to check if standard users can modify or replace them. Command: icacls 'C:\Program Files\Lenovo\<app>\*.exe'
    Affected if Standard users or the Users group have Modify or Write permissions on executable files, allowing substitution with malicious code
  5. Verify service binary path write access
    Check if the folder containing the service executable is writable by non-admin users. Use: Get-Acl 'C:\Program Files\Lenovo\<service>.exe' | Select-Object Access
    Affected if Service binary directory allows write access from low-privilege accounts who could replace the executable

A user is affected if Lenovo Display Control Center or Lenovo Accessories and Display Manager is installed AND non-administrative users have Write or Modify permissions on the application directories, service executables, or service configuration files.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-provided security patches for LDCC and LADM, or update to patched versions. Alternatively, restrict permissions on affected application directories and services to authenticated users only, removing write access for low-privilege accounts.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-2175 — 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-2175 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