CVE-2006-6346
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 · uneditedUnspecified vulnerability in SAP Internet Graphics Service (IGS) 6.40 Patchlevel 15 and earlier, and 7.00 Patchlevel 3 and earlier, allows remote attackers to cause a denial of service (service shutdown), obtain sensitive information (configuration files), and conduct certain other unauthorized activities, related to "Undocumented Features." NOTE: it is possible that there are multiple issues. This information is based upon a vague initial disclosure. Details will be updated after the grace period has ended. This is likely a different issue than 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 · moderate confidenceSAP Internet Graphics Service (IGS) versions 6.40 Patchlevel 15 and earlier, and 7.00 Patchlevel 3 and earlier contain unspecified 'undocumented features' that allow remote unauthenticated attackers to cause denial of service (service shutdown), obtain sensitive configuration file information, and conduct other unauthorized activities.
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<= 6.40_patch_15<= 7.00_patch_3CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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.
-
Verify if SAP IGS service is runningCheck running processes for sap igs executable or query SAP kernel processes. On Windows check Services panel for 'SAP Internet Graphics Service' or use command: tasklist | findstr -i igs. On Unix check for igs process: ps -ef | grep -i igsAffected if IGS service is running - the vulnerability only applies when the service is active
-
Identify installed IGS versionCheck the IGS version by examining the IGS binary or version file. Common locations: SAP kernel directory contains igs version files, or use SAP transaction SM51 to check kernel version including IGS components. Look for files named like 'igs_version' or check SAP NOTE references in the IGS directoryAffected if Version is 6.40 with Patchlevel 15 or lower, OR version is 7.00 with Patchlevel 3 or lower
-
Check for exposed IGS portsIdentify ports IGS is listening on (commonly 4000, 4001, or custom ports). Use netstat -an | findstr LISTENING or ss -tlnp to see listening ports. Verify if these ports are accessible from untrusted networksAffected if IGS HTTP/XML ports are exposed to unauthenticated remote attackers without firewall filtering
User is affected if SAP IGS service is running AND the installed version is 6.40 PL15 or earlier OR 7.00 PL3 or earlier AND the service is network-accessible to untrusted users.
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 SAP security patches for the affected IGS versions (6.40 PL15+, 7.00 PL3+) or disable the IGS service if not required in the SAP landscape, as this vulnerability allows remote attackers to cause DoS and access sensitive configuration files.
Latest supported SAP Internet Graphics Server (IGS) version - SAP has released multiple major versions since 6.x/7.x (2006), current versions include 7.5x and higher
- Identify the current SAP Internet Graphics Service (IGS) version in use
- For IGS 6.40.x: Upgrade to IGS 6.40 Patch 16 or later
- For IGS 7.00.x: Upgrade to IGS 7.00 Patch 4 or later
- Alternatively, upgrade to the latest available IGS version supported by SAP (current versions are significantly newer than 6.x/7.x from 2006)
- After upgrade, verify the IGS service is running and configuration files are accessible only to authorized users
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-6346 — 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-2006-6346 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