CVE-2008-0581
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 · uneditedGeert Moernaut LSrunasE allows local users to gain privileges by obtaining the encrypted password from a batch file, and constructing a modified batch file that specifies this password in the /password switch and specifies an arbitrary program in the /command switch.
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 confidenceLSrunasE stores encrypted passwords in batch files. Local users can extract these encrypted passwords and create modified batch files using the /password switch with the stolen password combined with the /command switch to specify an arbitrary program, achieving local privilege escalation.
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= 1.0= 1.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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/Au:N/C:C/I:C/A:C
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.
-
Check if LSrunasE or Supercrypt is installedSearch for Moernaut LSrunasE or Supercrypt executables on the system. Common locations may include C:\Program Files\ or directories where third-party utilities are stored. Look for lsrunase.exe or supercrypt.exe.Affected if Either Moernaut Lsrunase version 1.0 or Moernaut Supercrypt version 1.0 is installed on the system.
-
Locate batch files containing encrypted passwordsSearch for .bat or .cmd files that may have been created using LSrunasE. These files typically contain encrypted password strings. Look in user home directories, scheduled task folders, or application data directories.Affected if Batch files with encrypted password strings created by LSrunasE exist on the system.
-
Inspect batch files for /password switch usageExamine any found batch files for the presence of the /password switch followed by encrypted password strings. Open the files in a text editor to view their contents.Affected if Batch files contain the /password switch with encrypted credential data.
-
Identify batch files with /command switchSearch for batch files containing the /command switch which specifies the program to run. These would be the files an attacker could modify to execute arbitrary programs.Affected if Batch files using the /command switch to specify programs are present alongside /password switches.
-
Verify access controls on configuration and batch filesCheck file permissions on any LSrunasE-related configuration or batch files. Determine if standard users can read or modify these files.Affected if Non-privileged users can read encrypted passwords from batch files or modify batch files to inject arbitrary commands.
The environment is affected if Moernaut LSrunasE 1.0 or Supercrypt 1.0 is installed and batch files containing encrypted passwords with /password and /command switches are accessible to local users.
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 dataAvoid storing credentials in batch files; implement proper credential storage mechanisms, restrict access to configuration files containing credentials, and consider using Windows built-in privilege escalation methods instead of third-party tools.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-0581 — 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-2008-0581 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