dbcve.org
Netweaver As Internet Graphics ServerApplication · Sap

CVE-2021-27627

MEDIUM · 5.9 CVSS v3.1 Published 2021-06-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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 Service, versions - 7.20,7.20EXT,7.53,7.20_EX2,7.81, allows an unauthenticated attacker after retrieving an existing system state value can submit a malicious IGS request over a network which due to insufficient input validation in method ChartInterpreter::DoIt() which will trigger an internal memory corruption error in the system causing the system to crash and rendering it unavailable. In this attack, no data in the system can be viewed or modified.

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 Service (IGS) versions 7.20-7.81 contains a memory corruption vulnerability in the ChartInterpreter::DoIt() method. An unauthenticated attacker who first obtains an existing system state value can send a malicious IGS request. Due to insufficient input validation, this triggers memory corruption causing the affected SAP system to crash and become unavailable. The attack does not allow viewing or modifying data.

MitigationApply the relevant SAP Security Note (contact SAP support to obtain the appropriate patch for this vulnerability). If immediate patching is not feasible, consider restricting network access to the IGS service or disabling IGS if not required for business operations.

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
Netweaver As Internet Graphics ServerApplication
Affected:= 7.20= 7.20ex2= 7.20ext= 7.53= 7.81

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

CVSS:3.1/AV:N/AC:H/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. Check if SAP IGS is installed
    Query SAP system for installed components using transaction SPAM or check for IGS binaries in the SAP system directory (typically under /usr/sap/<SID>/SYS/exe/run/ or similar). Look for executables starting with 'igs' or 'igsmap'.
    Affected if IGS binaries or components are found on the system
  2. Identify the IGS version
    Use SAP transaction SM51 to list running server processes, or check the SAP kernel version by executing 'disp+work' version info. For IGS specifically, check the SAP NOTE implementation status or review the IGS-related kernel patches installed.
    Affected if The installed IGS version matches 7.20, 7.20ex2, 7.20ext, 7.53, or 7.81
  3. Verify IGS service is enabled
    Check SAP profile parameters for IGS configuration (parameters typically include icm/igs_* or via transaction SICF to verify IGS service paths are active). Also check if the IGS HTTP port is listening.
    Affected if IGS HTTP service (typically ports 8000-800n) is active and listening
  4. Determine network exposure of IGS port
    Run netstat or ss commands to check which network interfaces the IGS ports are bound to. Look for ports in the 8000 range. Check if they are bound to 0.0.0.0 (all interfaces) versus 127.0.0.1 (localhost only).
    Affected if IGS ports are accessible from network addresses other than localhost
  5. Confirm ChartInterpreter is accessible
    Test IGS functionality by making a request to the ChartInterpreter endpoint (typically /IGS/CHART/ or similar) via HTTP to verify the service responds. Use transaction SMICM to view ICM trace and verify IGS handling.
    Affected if HTTP requests to IGS ChartInterpreter endpoint succeed and return responses

A system is affected if SAP IGS is installed with versions 7.20, 7.20ex2, 7.20ext, 7.53, or 7.81 AND the IGS service is actively 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 Note (contact SAP support to obtain the appropriate patch for this vulnerability). If immediate patching is not feasible, consider restricting network access to the IGS service or disabling IGS if not required for business operations.

Fix this in Netweaver As Internet Graphics Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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