CVE-2023-28658
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 · uneditedInsecure inherited permissions in some Intel(R) oneMKL software before version 2022.0 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 confidenceIntel oneMKL before version 2022.0 contains insecure inherited permissions that allow an authenticated local user to potentially escalate privileges by exploiting improperly secured file system permissions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2022.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Detect if Intel oneMKL is installedCheck for the presence of Intel oneMKL by searching for oneMKL-related directories in common installation paths (e.g., /opt/intel, C:\Program Files\Intel\oneAPI) or by querying the system package manager if availableAffected if Intel oneMKL is present on the system
-
Identify the installed oneMKL versionLocate the oneMKL installation directory and look for version information in version files, DLL/so properties, or the installation path name itself. Common locations include version.txt, mkl_version.h, or the library files named with version stringsAffected if The version cannot be determined or is below 2022.0
-
Compare installed version against affected rangeParse the identified version number and compare it to the threshold 2022.0 using semantic versioning rulesAffected if The installed version is less than 2022.0 (e.g., 2021.x, 2020.x, or earlier)
-
Verify file system permissions on oneMKL directoriesInspect the permissions on the oneMKL installation directories and subdirectories. Check if non-privileged users have write access to directories or files that should be restricted to administrator or root accountsAffected if Authenticated local users have write access to sensitive oneMKL directories or configuration files that should be protected
The environment is affected if Intel oneMKL is installed with a version lower than 2022.0 and improper file system permissions allow unprivileged access to secure resources.
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 · scoped2022.0
Upgrade to Intel oneMKL version 2022.0 or later which contains the fix for insecure inherited permissions.
Intel oneMKL 2022.0
- Identify the currently installed version of Intel oneMKL using the package manager or Intel's installation utility
- Download Intel oneMKL version 2022.0 or later from the official Intel website or download center
- Uninstall the vulnerable oneMKL version following Intel's standard uninstallation procedures
- Install the downloaded version 2022.0 or later
- Verify the installed version matches the expected fixed version (2022.0 or later)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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 $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28658 — 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-2023-28658 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