CVE-2024-21799
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 · uneditedPath traversal for some Intel(R) Extension for Transformers software before version 1.5 may allow an authenticated user to potentially enable escalation of privilege via local access.
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 confidenceA path traversal vulnerability exists in Intel(R) Extension for Transformers software versions before 1.5. An authenticated user with local system access can potentially exploit directory traversal sequences to access files outside the intended directory boundaries, which could lead to privilege escalation.
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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Intel Extension for Transformers is installedCheck for the presence of the Intel Extension for Transformers software on the system. Look for installation directories, registered software, or run 'pip list' or similar package manager commands if installed via Python.Affected if The software is present on the system
-
Determine installed versionRetrieve the version number of Intel Extension for Transformers. Common methods include: 'pip show intel-extension-for-transformers', checking the installation manifest, or reviewing version metadata in the software directory.Affected if Version cannot be determined or is below 1.5
-
Compare version to affected rangeCompare the installed version against the affected range (versions before 1.5). Check if the version number is lower than 1.5.0 or 1.5.Affected if Installed version is 1.4.x or any version below 1.5
-
Verify local access and authentication contextDetermine if the system allows authenticated local user access to the software's file operation features. Review if local users or services can interact with the application's file handling capabilities.Affected if Authenticated local users can access the application's file operations
The environment is affected if Intel Extension for Transformers version below 1.5 is installed and authenticated local users can access its file operation features.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Intel(R) Extension for Transformers to version 1.5 or later. If upgrading is not immediately feasible, implement strict access controls and input validation on file operations within the affected software.
Intel(R) Extension for Transformers version 1.5
- 1. Identify the current version of Intel(R) Extension for Transformers installed on the system
- 2. Download Intel(R) Extension for Transformers version 1.5 or later from the official Intel source
- 3. Back up any existing configurations or data related to the current installation
- 4. Uninstall the current version of Intel Extension for Transformers
- 5. Install version 1.5 of Intel Extension for Transformers
- 6. Verify the installation was successful by checking the installed version
- 7. Restart any services or applications that use the Intel Extension for Transformers
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21799 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-21799 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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