CVE-2019-18193
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 · uneditedIn Unisys Stealth (core) 3.4.108.0, 3.4.209.x, 4.0.027.x and 4.0.114, key material inadvertently logged under certain conditions. Fixed included in 3.4.109, 4.0.027.13, 4.0.125 and 5.0.013.0.
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 confidenceIn Unisys Stealth (core) versions 3.4.108.0, 3.4.209.x, 4.0.027.x, and 4.0.114, cryptographic key material was inadvertently written to log files under certain conditions, potentially exposing sensitive encryption keys to unauthorized parties with log access.
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= 3.4.108.0= 3.4.209.0= 4.0.027.0= 4.0.114CVSS 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
- High
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/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 installed Unisys Stealth versionUse the Stealth version check command or examine the software installation details - typically via 'stealth --version', 'Get-StealthVersion' PowerShell cmdlet, or check the program files directory for version infoAffected if The installed version matches 3.4.108.0, 3.4.209.x, 4.0.027.x, or 4.0.114 exactly
-
Locate Stealth log directoriesCheck the default Stealth logging paths - commonly found in installation directories under /logs or /var/log/stealth, or in Windows Event Logs if configuredAffected if Log directories exist and contain logs from the affected versions
-
Search logs for cryptographic key patternsUse grep, Select-String, or similar tools to search log files for hexadecimal or base64 strings resembling cryptographic keys - look for patterns like 'BEGIN RSA PRIVATE KEY', long hexadecimal strings (32+ chars), or base64 blocks that decode to binary dataAffected if Log files contain any private key material, certificate private keys, or encryption keys that should not be exposed
-
Verify logging configurationExamine Stealth configuration files for logging settings - check if verbose logging or debug modes are enabled that might capture sensitive cryptographic operationsAffected if Logging is set to verbose or debug levels in the affected versions, increasing the likelihood of key material being logged
A defender is affected if Unisys Stealth version matches exactly 3.4.108.0, 3.4.209.0, 4.0.027.0, or 4.0.114 AND logs contain exposed cryptographic key material.
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 dataApply the vendor patches (3.4.109, 4.0.027.13, 4.0.125, or 5.0.013.0 depending on your branch) to remediate the key material logging. Review existing logs for potential key exposure.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-18193 — 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-2019-18193 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