CVE-2006-1039
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 Web Application Server (WebAS) Kernel before 7.0 allows remote attackers to inject arbitrary bytes into the HTTP response and obtain sensitive authentication information, or have other impacts, via a ";%20" followed by encoded HTTP headers.
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 confidenceThis is a header injection vulnerability in SAP Web Application Server (WebAS) Kernel versions prior to 7.0. Attackers can inject arbitrary bytes into HTTP responses by sending requests containing ';%20' followed by encoded HTTP headers. This allows remote attackers to manipulate HTTP response headers, potentially exposing sensitive authentication information or enabling further attacks such as session hijacking.
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.10= 6.20= 6.40CVSS 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
- None
AV:N/AC:L/Au:N/C:P/I:P/A:N
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.
-
Identify SAP WebAS Kernel versionExecute command 'sapcontrol -nr <instance> -function GetVersion' or check the 'kernel' directory for version files (e.g., 'disp+work' executable properties). On Windows, right-click the kernel executable and view version info.Affected if The installed version is 6.10, 6.20, or 6.40 (any version prior to 7.0)
-
Confirm HTTP service is activeUse transaction code SMICM (or ICMON in older versions) in SAP GUI to check if the ICM (Internet Communication Manager) is running and HTTP ports (typically 80, 443, or 5xx00) are active.Affected if HTTP service is enabled and listening on network interfaces accessible to users
-
Review HTTP access logs for injection attemptsExamine SAP ICM access logs (default location: /usr/sap/<SID>/<instance>/log/ or via transaction SM37 or log files in the work directory). Search for ';%20' pattern in query strings or headers.Affected if Recent logs contain requests with ';%20' followed by header-like content (e.g., 'Set-Cookie:', 'Location:')
-
Check for custom HTTP header configurationReview profile parameters icm/HTTP/mod_<x> in transaction RZ10 or via 'icmon' tool to see if custom headers are being added to responses dynamically.Affected if Custom header manipulation is configured and the SAP kernel is an affected version
You are affected if your SAP WebAS Kernel runs version 6.10, 6.20, or 6.40 AND the HTTP service (ICM) is enabled and exposed to network traffic.
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.
From vendor dataUpgrade SAP WebAS Kernel to version 7.0 or later, which contains the fix for this header injection vulnerability. Prior to upgrade, consider implementing Web Application Firewall (WAF) rules to detect and block requests containing ';%20' patterns in the query string.
- Consultation12.0 h
- Implementation24.0 h
- Testing32.0 h
- Review / QA12.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $21,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-1039 — 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-1039 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