Internet Graphics ServerApplication · Sap

CVE-2018-2421

HIGH · 7.5 CVSS v3.0 Published 2018-05-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
SAP Internet Graphics Server (IGS) Portwatcher, 7.20, 7.20EXT, 7.45, 7.49, 7.53, allows an attacker to prevent legitimate users from accessing a service, either by crashing or flooding the service.

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 · moderate confidence

SAP Internet Graphics Server (IGS) Portwatcher contains a denial-of-service vulnerability in versions 7.20, 7.20EXT, 7.45, 7.49, and 7.53. An unauthenticated attacker can exploit this to prevent legitimate users from accessing the service, either by crashing the Portwatcher service or by flooding it with malicious requests.

MitigationApply the relevant SAP security patch for this vulnerability. Organizations should review SAP Security Notes and implement appropriate updates to the affected IGS Portwatcher component.

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
Internet Graphics ServerApplication
Affected:= 7.20= 7.20ext= 7.45= 7.49= 7.53

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. Identify if SAP IGS Portwatcher is installed
    Check for the presence of SAP Internet Graphics Server installation directory or look for process 'portwatcher' or 'igwportwatcher' running on the system. On Windows, check Services for 'SAP Internet Graphics Server Portwatcher'. On Unix, use 'ps -ef | grep -i portwatcher'
    Affected if Portwatcher process or service is found running on the system
  2. Determine Portwatcher version
    Locate the IGS installation and check version information, typically found in the IGS executable or version file. Common locations include the 'exe' or 'bin' subdirectory within the SAP IGS installation path, or query the service directly if it supports version inquiry
    Affected if Version matches 7.20, 7.20EXT, 7.45, 7.49, or 7.53 exactly
  3. Verify Portwatcher is network accessible
    Check if Portwatcher is listening on configured ports (default IGS ports are typically 4000-4004 range). Use 'netstat -an' or 'ss -tlnp' to list listening ports and identify which are bound to external interfaces versus localhost only
    Affected if Portwatcher is listening on external/network interfaces, making it reachable by unauthenticated attackers
  4. Review Portwatcher logs for crash indicators
    Examine IGS log files in the 'work' or 'log' directory within the SAP IGS installation for recent crash dumps, unexpected restarts, or error messages related to Portwatcher. Check operating system event logs for application failures
    Affected if Recent crashes or abnormal restarts of Portwatcher service are found in logs

System is affected if SAP IGS Portwatcher is installed and the exact version is 7.20, 7.20EXT, 7.45, 7.49, or 7.53, regardless of whether it has already crashed from exploitation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant SAP security patch for this vulnerability. Organizations should review SAP Security Notes and implement appropriate updates to the affected IGS Portwatcher component.

Fix this in Internet Graphics Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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