CVE-2020-24620
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 · uneditedUnisys Stealth(core) before 4.0.134 stores passwords in a recoverable format. Therefore, a search of Enterprise Manager can potentially reveal credentials.
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 confidenceUnisys Stealth(core) versions prior to 4.0.134 store user credentials in a recoverable format rather than using proper cryptographic hashing or encryption. This allows anyone with access to the Enterprise Manager interface to search and retrieve plaintext passwords for stored accounts.
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.134CVSS 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.
-
Identify Unisys Stealth core versionLocate the installed version of Unisys Stealth core on the system, typically found in the application metadata, About section, or installation directory. Common methods include checking the Windows Programs list, looking in the installation folder for version files, or using the Enterprise Manager interface About/Help menu.Affected if The installed version is lower than 4.0.134 (e.g., 4.0.100, 3.5.x, etc.)
-
Verify Enterprise Manager accessConfirm that the Unisys Stealth Enterprise Manager interface is deployed and accessible. This could be a web-based console or desktop application depending on the deployment.Affected if Enterprise Manager is accessible to users who could search and retrieve stored account credentials
-
Check credential storage locationIf accessible, examine where Unisys Stealth stores user account credentials. This is typically in a configuration database, LDAP directory, or local user store used by the Stealth core services.Affected if Credentials are stored in any format other than salted cryptographic hashes (e.g., stored as plaintext, base64-encoded, or reversibly encrypted)
-
Test credential retrieval capabilityUsing an account with Enterprise Manager access, attempt to use the search or lookup feature to retrieve stored account passwords. Note whether passwords are displayed in plaintext.Affected if Plaintext passwords can be retrieved through the Enterprise Manager interface for any stored accounts
You are affected if Unisys Stealth core version is below 4.0.134 and the Enterprise Manager interface allows retrieval of plaintext passwords for stored accounts.
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 data4.0.134
Upgrade Unisys Stealth(core) to version 4.0.134 or later to obtain the patched build that properly protects credential storage. Additionally, rotate all credentials that may have been exposed through this vulnerability.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-24620 — 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-2020-24620 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