dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2024-4763

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 driver 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 to kernel.

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

This is a local privilege escalation vulnerability in Lenovo Display Control Center (LDCC) and Lenovo Accessories and Display Manager (LADM). The vulnerability exists in a driver component that fails to properly validate requests from user-mode processes, allowing a local attacker to elevate from standard user privileges to kernel-level access.

MitigationApply vendor updates from Lenovo for LDCC and LADM, or uninstall the affected software if updates are unavailable. Since this is a local privilege escalation, ensure untrusted users do not have local access to affected systems.

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. Identify if Lenovo Display Control Center is installed
    Open Windows Settings > Apps & Features (or Programs and Features) and search for 'Lenovo Display Control Center' or check Program Files for Lenovo folder. Alternatively, run 'Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like "*Display Control Center*"}' in PowerShell.
    Affected if The software is present on the system
  2. Identify if Lenovo Accessories and Display Manager is installed
    Search in Windows Apps & Features for 'Lenovo Accessories and Display Manager' or 'LADM'. Check for Lenovo folders in Program Files. Alternatively, run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName | Where-Object {$_.DisplayName -like "*Lenovo*"}'
    Affected if The software is present on the system
  3. Check for Lenovo driver components
    Open Device Manager and look for any Lenovo display or monitor-related drivers under 'Display adapters' or 'Monitors'. Also check C:\Windows\System32\drivers for Lenovo driver files (typically .sys files with Lenovo naming). Run 'driverquery /v | findstr -i lenovo'
    Affected if Lenovo display/monitor drivers are present and loaded
  4. Determine installed version of LDCC or LADM
    Right-click the installed application in Apps & Features and select 'Advanced options' to view version, or locate the main executable (typically in C:\Program Files\Lenovo\ or C:\Program Files (x86)\Lenovo\) right-click properties to check version info.
    Affected if Version cannot be determined or is unknown/old
  5. Verify if running as standard user with access to affected system
    Confirm you are logged in as a non-administrator standard user account. Run 'whoami /groups | findstr "BUILTIN\\Administrators"' - if not present, you are a standard user.
    Affected if Running as standard user with local access to a system with affected Lenovo software installed

A system is affected if Lenovo Display Control Center or Lenovo Accessories and Display Manager is installed and the vulnerable Lenovo driver component is present, allowing a local standard user to potentially escalate to kernel privileges.

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 updates from Lenovo for LDCC and LADM, or uninstall the affected software if updates are unavailable. Since this is a local privilege escalation, ensure untrusted users do not have local access to affected systems.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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