CVE-2023-29189
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 CRM (WebClient UI) - versions S4FND 102, 103, 104, 105, 106, 107, WEBCUIF, 700, 701, 731, 730, 746, 747, 748, 800, 801, allows an authenticated attacker to modify HTTP verbs used in requests to the web server. This application is exposed over the network and successful exploitation can lead to exposure of form fields
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 CRM WebClient UI fails to properly validate or restrict HTTP verbs in requests, allowing an authenticated attacker to modify the HTTP method (GET, POST, PUT, DELETE, etc.) and potentially access or manipulate form fields in unintended ways. This is a web layer vulnerability in the Internet Communication Framework (ICF).
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= 102= 103= 104= 105= 700= 701= 730= 731= 746= 747= 748= 800= 801CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 installed SAP CRM WebClient UI versionUsing SAP transaction code SM37 or SPAM/SAINT, check the installed version of the WebClient UI component. Compare against the affected versions: 700, 701, 730, 731, 746, 747, 748, 800, 801.Affected if The installed WebClient UI version matches one of the listed affected versions.
-
Identify installed SAP S4fnd versionUsing SAP transaction code SM37 or SPAM/SAINT, check the installed version of the S4fnd component. Compare against the affected versions: 102, 103, 104, 105.Affected if The installed S4fnd version matches one of the listed affected versions.
-
Verify ICF services are active for WebClient UIUsing SAP transaction code SICF, check if the ICF nodes related to WebClient UI (such as /sap/bc/webdynpro/sap/crm_ui*) are active. Navigate to the relevant ICF service tree for CRM WebClient UI.Affected if ICF services for CRM WebClient UI are active and accessible via HTTP/HTTPS.
-
Inspect HTTP method handling configurationUsing transaction code SICF, select the relevant WebClient UI ICF node and examine the 'Handler List' and 'Logon' settings. Check if there are specific HTTP verb restrictions configured or if all verbs are permitted by default.Affected if HTTP verb validation is not explicitly configured or restricted, allowing arbitrary HTTP methods to be processed.
A user is affected if they have SAP CRM WebClient UI or S4fnd installed with a version matching the affected list AND the ICF WebClient UI services are active with default or missing HTTP verb validation.
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 note/patch for CVE-2023-29189 and configure proper HTTP verb validation at the application and web server level to ensure form fields cannot be accessed or manipulated via unexpected HTTP methods.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-29189 — 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-29189 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