CVE-2024-28881
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 · uneditedUncontrolled search path for some Intel(R) Fortran Compiler Classic software before version 2021.13 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 · high confidenceThis is an uncontrolled search path (DLL/library hijacking) vulnerability in Intel Fortran Compiler Classic versions prior to 2021.13. An authenticated local user could place malicious libraries in a path the compiler searches, causing arbitrary code execution with elevated privileges when the compiler runs.
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
- High
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Locate Intel Fortran Compiler Classic installationSearch for the ifort compiler executable (typically named ifort.exe on Windows or ifort on Linux) in common Intel compiler installation directories such as C:\Program Files\Intel\oneAPI\ or /opt/intel/Affected if Intel Fortran Compiler Classic is present on the system
-
Determine the installed version numberRun 'ifort --version' or check the compiler's About/Version information in the IDE, or examine the installer metadata in the installation directoryAffected if The version returned is less than 2021.13 (e.g., 2021.12, 2021.11, etc.)
-
Verify the DLL/library search path configurationExamine the compiler's library paths by running 'ifort -print-search-dirs' or reviewing environment variables such as LIB, PATH, or compiler-specific variables like IFPATH that define where the compiler searches for librariesAffected if Directories in the search path are writable by untrusted local users
The environment is affected if Intel Fortran Compiler Classic version is prior to 2021.13 and untrusted local users can place files in directories the compiler uses to search for libraries or DLLs.
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 to Intel Fortran Compiler Classic version 2021.13 or later from Intel's official distribution channels to obtain the vendor patch.
Intel Fortran Compiler Classic 2021.13 or later
- 1. Identify the current version of Intel Fortran Compiler Classic installed on the system
- 2. Download Intel Fortran Compiler Classic version 2021.13 or later from the official Intel website (intel.com)
- 3. Verify the integrity of the downloaded installer using checksums if provided
- 4. Backup any existing projects or compiler configurations before upgrading
- 5. Uninstall the current version of Intel Fortran Compiler Classic
- 6. Install the new version (2021.13 or later) with appropriate administrator privileges
- 7. Verify the installation was successful and the version number is correct
- 8. Reconfigure any build scripts or environment variables as needed to point to the new compiler path
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28881 — 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-28881 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