CVE-2023-29108
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 · uneditedThe IP filter in ABAP Platform and SAP Web Dispatcher - versions WEBDISP 7.85, 7.89, KERNEL 7.85, 7.89, 7.91, may be vulnerable by erroneous IP netmask handling. This may enable access to backend applications from unwanted sources.
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 confidenceThe IP filter in SAP Web Dispatcher and ABAP Platform contains erroneous netmask handling that may incorrectly evaluate IP addresses, potentially allowing unauthorized sources to access backend applications through the dispatcher.
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.85= 7.89= 7.91= 7.85= 7.89CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 Web Dispatcher installationLocate the SAP Web Dispatcher binary (sapwebdisp) and check its version by running 'sapwebdisp -v' or examining the profile files in the global SAP profile directory (default: /usr/sap/<SID>/SYS/profile/)Affected if The installed version matches 7.85 or 7.89 and IP filtering is configured
-
Identify ABAP Platform Kernel versionCheck the kernel version by running 'disp+work -v' or examining the kernel binaries in /usr/sap/<SID>/SYS/exe/run/Affected if The kernel version matches 7.85, 7.89, or 7.91 and IP filtering is in use
-
Verify IP filter configurationReview the SAP profile parameters for ICM/HTTP filtering: look for 'icm/HTTP/filter' or 'icm/host_bind_local' directives in the instance profile (DEFAULT.PFL) and the instance-specific profileAffected if IP filter rules are defined using netmask notation (CIDR or subnet masks) in the Web Dispatcher or ICM configuration
-
Inspect netmask entries in IP filter rulesExamine the IP filter rule files referenced by the icm/HTTP/filter parameter, or check the profile parameters icm/accept_<host> and icm/reject_<host> for netmask definitionsAffected if Any netmask-based IP filter rules are configured that could be incorrectly evaluated due to the bug
You are affected if you run SAP Web Dispatcher versions 7.85 or 7.89, or ABAP Platform Kernel versions 7.85, 7.89, or 7.91, and have IP filter rules configured with netmask notation that may be evaluated incorrectly.
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 dataApply the relevant SAP security patch and review IP filter rules to ensure netmask configurations are correct and restrict access to authorized IP ranges only.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.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 $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-29108 — 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-2023-29108 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