CVE-2022-26660
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 · uneditedRunAsSpc 4.0 uses a universal and recoverable encryption key. In possession of a file encrypted by RunAsSpc, an attacker can recover the credentials that were used.
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 confidenceRunAsSpc 4.0 implements a weak cryptographic scheme using a universal, recoverable encryption key that is identical across all installations. An attacker who obtains an encrypted file can decrypt it using this known key, revealing the stored credentials.
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= 4.0.0.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 RunAsSpc installation and versionCheck for the presence of RunAsSpc.exe or Runasspc.exe in the system (common paths: C:\Program Files\RunAsSpc, C:\Program Files (x86)\RunAsSpc, or the directory where it was installed). Right-click the executable, select Properties, and verify the File Version on the Details tab.Affected if The installed version is exactly 4.0.0.0
-
Identify encrypted credential filesSearch for .spc files on the system (these are the encrypted credential storage files used by RunAsSpc). Use the command: dir /s /b C:\*.spc or search with your endpoint detection tools for files with .spc extension.Affected if Any .spc files exist on the system, indicating credentials were stored using this software
-
Check for scheduled tasks using RunAsSpcReview Windows scheduled tasks for entries that invoke RunAsSpc/Runasspc.exe with credential parameters. Use: schtasks /query /fo LIST /v or check Task Scheduler GUI for tasks with RunAsSpc in the action or program path.Affected if Scheduled tasks reference RunAsSpc and likely execute with stored credentials
You are affected if RunAsSpc version 4.0.0.0 is installed and you have .spc encrypted credential files or scheduled tasks that rely on stored credentials within this software.
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 dataUntil a vendor patch is available, avoid using RunAsSpc to store sensitive credentials, or rotate any credentials that may have been stored using this software. The vendor should implement unique, securely-generated per-instance encryption keys with proper key management.
- Consultation6.0 h
- Implementation20.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26660 — 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-26660 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