CVE-2022-26344
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 · uneditedIncorrect default permissions in the installation binaries for Intel(R) SEAPI all versions 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(R) SEAPI installation binaries have overly permissive default file permissions that allow authenticated local users to modify or replace executable files. This permission misconfiguration can be exploited to achieve privilege escalation by injecting malicious code into privileged binaries.
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 dataall versionsCVSS 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.
-
Locate Intel SEAPI installation directorySearch for Intel SEAPI-related files and directories. Common locations include C:\Program Files\Intel\, C:\Program Files (x86)\Intel\, or /opt/intel/ on Linux. Use commands like 'dir /s /b *SEAPI*' on Windows or 'find / -iname "*seapi*" 2>/dev/null' on Linux.Affected if SEAPI installation directory or executables are found on the system
-
Identify SEAPI executable filesWithin the SEAPI installation directory, enumerate all .exe, .dll, .sys, or binary files. List all files that appear to be part of the SEAPI installation.Affected if SEAPI executable files exist on the system
-
Check file permissions on SEAPI binariesReview the access control list or file permissions on each SEAPI executable. On Windows, use 'icacls <filename>' or check Security properties. On Linux, use 'ls -la' or 'getfacl' to examine permissions.Affected if Any SEAPI executable grants write or modify permissions to Users, Authenticated Users, or other non-privileged groups
-
Verify non-privileged user write accessTest or inspect whether standard user accounts can write to, modify, or replace SEAPI executable files. On Windows, attempt to modify as a non-admin user or review effective permissions. On Linux, check if files are group-writable or world-writable.Affected if Non-privileged users have write, modify, or replace permissions on SEAPI executable files
-
Check SEAPI service binary permissionsIf SEAPI runs as a Windows service or daemon, examine the service binary permissions. Use 'sc qc <service>' and 'icacls' on the service executable path.Affected if The service binary or its parent directory allows modification by non-privileged users
If Intel SEAPI is installed and any of its executable files or directories grant write or modify permissions to non-privileged users, the system is affected by CVE-2022-26344 and vulnerable to privilege escalation.
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.
From vendor dataCorrect the default permissions on Intel(R) SEAPI installation binaries to follow the principle of least privilege, removing write access for non-privileged users. Reinstall or reapply correct permissions to affected binaries.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26344 — 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-2022-26344 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