dbcve.org
Internet Graphics ServerApplication · Sap

CVE-2018-2385

MEDIUM · 6.5 CVSS v3.0 Published 2018-02-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Under certain conditions a malicious user provoking a divide by zero crash can prevent legitimate users from accessing the SAP Internet Graphics Server, 7.20, 7.20EXT, 7.45, 7.49, 7.53, and its services.

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

This is a Denial of Service vulnerability in SAP Internet Graphics Server where a malicious user can trigger a divide by zero condition causing a crash that prevents legitimate users from accessing the server and its services. The vulnerability affects versions 7.20, 7.20EXT, 7.45, 7.49, and 7.53.

MitigationApply the relevant SAP security patch when available. Implement network-level access controls to limit exposure to untrusted users and consider rate limiting or web application firewall rules to help mitigate abuse until the patch is applied.

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

CVSS:3.0/AV:N/AC:L/PR:L/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 Internet Graphics Server is installed
    Check for the presence of SAP IGS components on the system. Common locations include the SAP installation directory (e.g., /sapmnt/<SID>/igs on Unix or C:\sapmnt\<SID>\igs on Windows). Look for igs executable files or the IGS service.
    Affected if SAP IGS is not found on the system - not vulnerable. If found, proceed to version check.
  2. Determine the installed IGS version
    Locate the IGS version information. This is typically stored in a version file, manifest, or can be retrieved via the SAP IGS administration interface if available. Common file names include version.txt, sapigs.ctl, or check the executable properties of the igs binary.
    Affected if The installed version must be exactly 7.20, 7.20EXT, 7.45, 7.49, or 7.53 to be vulnerable. Other versions are not affected by this specific CVE.
  3. Verify the IGS service is running and accessible
    Check if the SAP Internet Graphics Server process is active and listening on its configured port (typically ports 4000-4004 or as configured in the SAP system). Use system commands like 'ps -ef' on Unix or check Windows services to confirm the IGS service status.
    Affected if The vulnerability is only exploitable when the IGS service is running and network-accessible. If the service is stopped or disabled, the DoS cannot be triggered.
  4. Assess network exposure of the IGS service
    Review network configuration to determine if the IGS ports are exposed to untrusted networks. Check firewall rules, SAP router configuration, and load balancer settings to identify if the IGS service can be reached from outside the trusted network.
    Affected if If the IGS service is reachable from untrusted networks or the internet, the vulnerability can be exploited by remote attackers. Restrict network access to trusted users to reduce exposure.

Your environment is affected if SAP Internet Graphics Server is installed, the version is exactly 7.20, 7.20EXT, 7.45, 7.49, or 7.53, and the IGS service is running and 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant SAP security patch when available. Implement network-level access controls to limit exposure to untrusted users and consider rate limiting or web application firewall rules to help mitigate abuse until the patch is applied.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-2385 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2385 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