StealthApplication · Unisys

CVE-2021-3141

HIGH · 7.8 CVSS v3.1 Published 2021-03-18
Fix available
A fix is available. Upgrade to 6.0.025.0 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
In Unisys Stealth (core) before 6.0.025.0, the Keycloak password is stored in a recoverable format that might be accessible by a local attacker, who could gain access to the Management Server and change the Stealth configuration.

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 confidence

In Unisys Stealth (core) versions before 6.0.025.0, the Keycloak password is stored in a recoverable format rather than being properly hashed or encrypted. A local attacker with access to the system could recover this password and gain unauthorized access to the Management Server, allowing them to modify Stealth configuration settings.

MitigationUpgrade Unisys Stealth to version 6.0.025.0 or later, which implements proper password storage. If immediate patching is not possible, restrict local access to systems storing these credentials and monitor for unauthorized access to the Management Server.

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
StealthApplication
Affected:>= 6.0, < 6.0.025.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Unisys Stealth version
    Use the product's built-in version reporting mechanism or check the Stealth installation directory for version metadata files
    Affected if The installed version is 6.0 or higher but lower than 6.0.025.0
  2. Locate Keycloak configuration files
    Search for Keycloak-related configuration files in the Stealth installation directory, typically under the configuration or conf subdirectory
    Affected if Configuration files containing Keycloak password entries exist and are readable by local users
  3. Inspect password storage format
    Examine the Keycloak password configuration value in the relevant config file. Determine if the password appears as plaintext, base64-encoded, reversibly encrypted, or in another recoverable format rather than being stored as a salted hash
    Affected if The password value is stored in a recoverable encoding (plaintext, base64, reversible encryption) instead of a one-way hash
  4. Verify file system permissions on credential files
    Check file system permissions on the Keycloak configuration files and any associated credential stores. Use standard OS permission checking tools to verify who can read these files
    Affected if Non-administrator local users have read access to files containing the Keycloak password
  5. Confirm Management Server accessibility
    Verify that the Management Server component is configured and accessible from the system being checked
    Affected if The Management Server is reachable and the recoverable password could be used to authenticate to it

A system is affected if Unisys Stealth version 6.0 through 6.0.025.0 is installed and Keycloak credentials are stored in a recoverable (non-hashed) format accessible to local users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 6.0.025.0 or later
Fixed in 6.0.025.0
Interim mitigation

Upgrade Unisys Stealth to version 6.0.025.0 or later, which implements proper password storage. If immediate patching is not possible, restrict local access to systems storing these credentials and monitor for unauthorized access to the Management Server.

Fix this in Stealth Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-3141 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-3141 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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