Stealth SvgApplication · Unisys

CVE-2018-8049

HIGH · 7.5 CVSS v3.0 Published 2018-04-03
Fix available
A fix is available. Upgrade to 3.0.1999 / 3.2.030 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
The Stealth endpoint in Unisys Stealth SVG 2.8.x, 3.0.x before 3.0.1999, 3.1.x, 3.2.x before 3.2.030, and 3.3.x before 3.3.016, when running on Linux and AIX, allows remote attackers to cause a denial of service (crash) via crafted packets.

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

The Stealth endpoint in Unisys Stealth SVG versions 2.8.x, 3.0.x before 3.0.1999, 3.1.x, 3.2.x before 3.2.030, and 3.3.x before 3.3.016 running on Linux and AIX platforms contains a vulnerability that allows remote attackers to crash the service via specially crafted network packets.

MitigationApply the vendor patches: upgrade to version 3.0.1999 or later for 3.0.x, 3.2.030 or later for 3.2.x, and 3.3.016 or later for 3.3.x. Consider network segmentation or firewall rules to limit exposure to untrusted networks until patching is completed.

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
Stealth SvgApplication
Affected:>= 3.0, < 3.0.1999>= 3.2, < 3.2.030>= 3.3, < 3.3.016= 2.8

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Verify Unisys Stealth SVG is installed
    Check for the presence of Unisys Stealth software on the system. Common locations include /opt/unisys/stealth or check for stealth-related processes using 'ps aux | grep -i stealth' or 'lsnode -a' on AIX.
    Affected if The software is not found or no stealth processes are running.
  2. Identify the installed version
    Run the command to check the Stealth version, typically found in a version file or via a stealth-specific command. Common paths include /opt/unisys/stealth/version or check the Stealth service banner.
    Affected if The version cannot be determined or the software is not installed.
  3. Compare version against affected ranges
    Match the installed version number to the affected ranges: 2.8.x (all), 3.0.x before 3.0.1999, 3.1.x (all), 3.2.x before 3.2.030, 3.3.x before 3.3.016.
    Affected if The installed version falls within any of these vulnerable ranges.
  4. Confirm platform is Linux or AIX
    Run 'uname -a' or 'oslevel' (AIX) to identify the operating system. This vulnerability only affects Linux and AIX platforms.
    Affected if The platform is Linux or AIX AND the version is in the affected ranges.
  5. Check if Stealth endpoint is network accessible
    Review network configuration and firewall rules to determine if the Stealth service port is exposed to network access. Check for listening ports related to stealth using 'netstat -anp' or 'ss -tulpn'.
    Affected if The Stealth service is network-accessible and the version/platform conditions are met.

You are affected if Unisys Stealth SVG is installed on Linux or AIX with a version in the 2.8.x, 3.0.x (<3.0.1999), 3.1.x, 3.2.x (<3.2.030), or 3.3.x (<3.3.016) ranges and the service is network-accessible.

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 3.0.1999 / 3.2.030 / 3.3.016 or later
Fixed in 3.0.19993.2.0303.3.016
Interim mitigation

Apply the vendor patches: upgrade to version 3.0.1999 or later for 3.0.x, 3.2.030 or later for 3.2.x, and 3.3.016 or later for 3.3.x. Consider network segmentation or firewall rules to limit exposure to untrusted networks until patching is completed.

Fix this in Stealth Svg Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-8049 — 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-2018-8049 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