# CVE-2024-12673: Privilege escalation in Vantage

> A local attacker can elevate privileges via an improper privilege vulnerability in the BIOS customization feature of Lenovo Vantage.

- **Severity:** High 8.5 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Feb 2025
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-3hxq-f9p6-ww56

## What is CVE-2024-12673?

CVE-2024-12673 is a high-severity vulnerability in Lenovo Vantage, published on 12 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An improper privilege vulnerability was reported in a BIOS customization feature of Lenovo Vantage on SMB notebook devices which could allow a local attacker to elevate privileges on the system.

This vulnerability only affects Vantage installed on these devices:

  *  Lenovo V Series (Gen 5)
  *  ThinkBook 14 (Gen 6, 7)
  *  ThinkBook 16 (Gen 6, 7)
  *  ThinkPad E Series (Gen 1)

Weakness: CWE-250 (Execution with Unnecessary Privileges)

## Which versions are affected by CVE-2024-12673?


## How do I fix CVE-2024-12673?

No fix has been published for CVE-2024-12673 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-12673 being exploited?

There is no known exploitation of CVE-2024-12673 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-12673 and fix it if it is affected.

What it is: CVE-2024-12673 is a high-severity vulnerability in Lenovo Vantage, published on 12 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-12673 in the wild and no public exploit code.

Affected product: Lenovo Vantage. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-12673/ (Markdown: https://insights.sbomify.com/CVE-2024-12673/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-12673
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-12673
- OSV: https://osv.dev/vulnerability/CVE-2024-12673

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-12673/
Summaries are generated and may contain mistakes; the official description above is the record.