dbcve.org
Link Following (Symlink)Weakness · CWE-59

CVE-2025-24918

MEDIUM · 6.7 CVSS v3.1 Published 2025-11-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated

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
Improper link resolution before file access ('link following') for some Intel(R) Server Configuration Utility software and Intel(R) Server Firmware Update Utility software before version 16.0.12. within Ring 3: User Applications may allow an escalation of privilege. System software adversary with an authenticated user combined with a high complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are present without special internal knowledge and requires active user interaction. The potential vulnerability may impact the confidentiality (high), integrity (high) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.

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 confidence

This is a link following (symlink attack) vulnerability in Intel Server Configuration Utility and Intel Server Firmware Update Utility software versions prior to 16.0.12. The vulnerability allows an authenticated local user with high-complexity attack requirements to potentially escalate privileges by exploiting improper link resolution before file access.

MitigationUpgrade Intel Server Configuration Utility and Server Firmware Update Utility to version 16.0.12 or later to remediate this vulnerability.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Intel Server Configuration Utility is installed
    Check for the presence of Intel Server Configuration Utility or Intel Server Firmware Update Utility in the system. Look in standard software installation directories or check the system's installed programs list.
    Affected if Either product is found on the system
  2. Determine the installed version of the Intel utility
    Locate the installed executable or check the software's version information (typically via file properties, installed programs list, or registry entry). Record the exact version number.
    Affected if The exact version number is obtained and is less than 16.0.12
  3. Compare version against the affected range
    Compare your installed version to the affected range: versions prior to 16.0.12 are vulnerable, version 16.0.12 and later are not.
    Affected if Installed version is any version prior to 16.0.12 (e.g., 16.0.11, 16.0.10, earlier versions)
  4. Confirm the software is in use or executable on the system
    Verify the software executable exists and is accessible on the local system, as the vulnerability requires the utility to be present and executable.
    Affected if The vulnerable utility software is present and executable on the system

A user is affected if Intel Server Configuration Utility or Intel Server Firmware Update Utility is installed with any version prior to 16.0.12, as the symlink link-following vulnerability exists only in those versions.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Intel Server Configuration Utility and Server Firmware Update Utility to version 16.0.12 or later to remediate this vulnerability.

Recommended fix Moderate confidence

16.0.12 or later

  1. Navigate to the Intel Support website and locate the Intel Server Configuration Utility and/or Intel Server Firmware Update Utility software
  2. Download version 16.0.12 or later of the affected software
  3. Follow Intel's standard installation procedures to apply the update
  4. Verify the installed version matches 16.0.12 or later after installation

Generated from the published advisory — verify against the referenced sources before acting.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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