dbcve.org
Internet Graphics ServerApplication · Sap

CVE-2006-4133

HIGH · 7.5 CVSS v2.0 Published 2006-08-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Heap-based buffer overflow in SAP Internet Graphics Service (IGS) 6.40 and earlier, and 7.00 and earlier, allows remote attackers to cause a denial of service (crash) or execute arbitrary code via an HTTP request with an ADM:GETLOGFILE command and a long portwatcher argument, which triggers the overflow during error message construction when the _snprintf function returns a negative value that is used in a memcpy operation.

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

Heap-based buffer overflow in SAP Internet Graphics Service (IGS) versions 6.40 and earlier and 7.00 and earlier. The vulnerability is triggered by an HTTP request containing the ADM:GETLOGFILE command with an oversized portwatcher argument. The overflow occurs because _snprintf returns a negative value when the formatted output exceeds the buffer size, and this negative value is incorrectly used as the length parameter in a memcpy call, corrupting heap memory and allowing denial of service or arbitrary code execution.

MitigationApply the relevant SAP security patch for CVE-2006-4133. Until patched, restrict network access to SAP IGS to trusted sources only to reduce attack surface.

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= 6.40_patch_11= 6.40_patch_15= 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 the presence of SAP Internet Graphics Service by looking for its executable or service. Common installation paths include /sapmnt/<SID>/igs or C:\sapmnt\<SID>\igs on Windows. On Linux/Unix, search for 'igsw' or 'igs' processes running.
    Affected if SAP IGS software is present on the system
  2. Determine the SAP IGS version
    Run the IGS executable with version information, or check the SAP bundle version. Typically you can find version information in the SAP system info using transaction SM51 or by checking the IGS binary directly if accessible.
    Affected if Installed version is 6.40 or earlier, or 7.00 or earlier, including specific patch levels 6.40_patch_11, 6.40_patch_15, or 7.00_patch_3
  3. Verify the HTTP service for IGS is enabled
    Check if the SAP IGS HTTP port is listening. Default SAP IGS HTTP runs on port 8000 (though it may vary). Use netstat or similar to check if port 8000 or configured IGS HTTP port is in LISTEN state.
    Affected if The IGS HTTP service is exposed and listening on a network port
  4. Confirm the ADM command handler is accessible
    Test if the vulnerable ADM:GETLOGFILE endpoint is reachable by sending a crafted HTTP request to the IGS server. The endpoint typically responds to requests at /adm/getlogfile or similar paths under the ADM servlet.
    Affected if The ADM servlet or getlogfile command handler is accessible and responds to HTTP requests

A system is affected if it runs SAP IGS versions 6.40 or 7.00 (including the listed patch levels) with the HTTP service enabled and the ADM command handler accessible, allowing an attacker to send a specially crafted ADM:GETLOGFILE request with an oversized portwatcher argument to trigger the heap overflow.

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 for CVE-2006-4133. Until patched, restrict network access to SAP IGS to trusted sources only to reduce attack surface.

Fix this in Internet Graphics Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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