CVE-2018-2420
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 · uneditedSAP Internet Graphics Server (IGS), 7.20, 7.20EXT, 7.45, 7.49, 7.53, allows an attacker to upload any file (including script files) without proper file format validation.
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 confidenceSAP Internet Graphics Server (IGS) contains an arbitrary file upload vulnerability where insufficient file format validation allows attackers to upload any file type, including malicious script files, without proper validation checks.
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= 7.20= 7.20ext= 7.45= 7.49= 7.53CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/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.
-
Confirm SAP Internet Graphics Server installationLocate the SAP IGS binaries and executable. On Windows this is typically under the SAP installation directory (e.g., /usr/sap/<SID>/SCS/exe for Unix or the corresponding Windows path). Look for executables like igs_monitor, igs_helper, or the IMC (Internet Graphics Server) service.Affected if SAP Internet Graphics Server is installed on the system.
-
Identify installed IGS versionRun the version check command for the IGS executable. In SAP systems this can often be obtained via SM51 (SAP Instances) or by executing the igs version command from the IGS binary directory. Alternatively, check the SAP Note referenced for this CVE or review the SAP IGS version information in the SAP System Properties (transaction SM37 or by examining the igs version file in the installation directory.Affected if The installed IGS version matches exactly 7.20, 7.20ext, 7.45, 7.49, or 7.53.
-
Verify IMC HTTP service is activeCheck if the Internet Graphics Server IMC (Image Management Channel) HTTP service is running. This can be verified via SAP transaction SMICM (ICM Monitor) or by checking if port 8000 (default IGS HTTP port) or the configured IMC port is listening. Use netstat or similar tools to confirm the service is active.Affected if The IMC HTTP service is running and accepting connections on the configured port.
-
Inspect file upload configurationReview the ICM/IGS configuration files (typically icm.ini or the IGS-specific configuration) for file upload handling settings. Look for parameters related to file upload validation, allowed file types, or upload functionality. Check the SAP IGS administration settings accessible via transaction SXI_CACHE or the IGS administrative console.Affected if File upload functionality is enabled in the IGS configuration without proper file type validation or allowlist controls.
A system is affected if SAP Internet Graphics Server is installed with version 7.20, 7.20ext, 7.45, 7.49, or 7.53 and the IMC HTTP service is running with file upload capabilities exposed.
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.
dbcve · scopedApply the relevant SAP security patch for CVE-2018-2420 and implement strict file format validation with allowlist controls to restrict uploads to only permitted file types.
SAP IGS version 7.53 or later
- 1. Check the current SAP IGS version using SAP transaction SM51 or by querying the IGS version via the SAP Management Console.
- 2. Obtain the latest SAP IGS version from SAP Support Portal (support.sap.com) - the official description mentions version 7.53 and later as containing the fix.
- 3. Apply the relevant SAP Security Note for CVE-2018-2420 from the SAP Security Patch Day or request the hotfix via SAP Support.
- 4. After applying the patch, verify the file upload restrictions are enforced by attempting to upload a non-image file to the IGS (test in non-production first).
- 5. Confirm the fix by checking the IGS version shows the patched release.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-2420 — 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-2018-2420 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