Internet Graphics ServerApplication · Sap

CVE-2006-6345

HIGH · 7.5 CVSS v2.0 Published 2006-12-07
Fix available
A fix is available. Upgrade to after 7.00_patch_3 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
Directory traversal vulnerability in SAP Internet Graphics Service (IGS) 6.40 Patchlevel 16 and earlier, and 7.00 Patchlevel 6 and earlier, allows remote attackers to delete arbitrary files via directory traversal sequences in an HTTP request. NOTE: This information is based upon an initial disclosure. Details will be updated after the grace period has ended. This issue is different from CVE-2006-4133 and CVE-2006-4134.

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

A directory traversal vulnerability in SAP Internet Graphics Service (IGS) versions 6.40 Patchlevel 16 and earlier, and 7.00 Patchlevel 6 and earlier, allows remote attackers to delete arbitrary files on the server by using directory traversal sequences (such as '../') in HTTP requests. The vulnerability is exploitable remotely via specially crafted HTTP requests.

MitigationApply the relevant SAP security patch for this vulnerability to the affected IGS installations. Additionally, network-level restrictions should be implemented to limit access to the IGS HTTP ports to trusted sources only.

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:<= 6.40_patch_16<= 7.00_patch_3

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
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

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 is installed
    Check for SAP Internet Graphics Service processes or installation directories. Common locations: /sapmnt/SID/profile/, /usr/sap/, or look for 'IGS' in running SAP processes using 'ps -ef | grep -i igs' or 'tasklist | findstr igs' on Windows.
    Affected if No IGS process or installation found means not affected by this CVE.
  2. Determine the IGS version
    Check the IGS version via SAP transaction code 'SM51' for running instances, or check the SAP kernel version in the /sapmnt/SID/exe directory, or query the IGS HTTP server version by accessing the IGS port (commonly port 4000) and checking the server banner.
    Affected if IGS version 6.40 with Patchlevel 16 or lower, OR version 7.00 with Patchlevel 3 or lower indicates vulnerability to this CVE.
  3. Verify if HTTP interface is enabled for IGS
    Check if the IGS HTTP port (default port 4000) is listening and accessible. Use 'netstat -an | grep 4000' or 'telnet localhost 4000' to test connectivity. Also verify icm/HTTP/strip_root_path parameter in the IGS configuration.
    Affected if HTTP port 4000 is open and accessible means the directory traversal vulnerability is exploitable remotely.
  4. Confirm IGS configuration allows directory traversal
    Review the IGS configuration files (typically igs.xml or icm.ini) for the 'allowDirectoryBrowsing' or path traversal restrictions. Check the ICM/IGS parameter settings in the SAP system profile using transaction 'RZ10'.
    Affected if No restrictions on path traversal in IGS configuration combined with vulnerable version means the system is affected.

Your environment is affected if SAP IGS is installed with version 6.40 patchlevel 16 or lower or version 7.00 patchlevel 3 or lower, AND the IGS HTTP service is accessible on the network.

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 a release after 7.00_patch_3
Interim mitigation

Apply the relevant SAP security patch for this vulnerability to the affected IGS installations. Additionally, network-level restrictions should be implemented to limit access to the IGS HTTP ports to trusted sources only.

Fix this in Internet Graphics Server Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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