CVE-2024-21736
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 S/4HANA Finance for (Advanced Payment Management) - versions SAPSCORE 128, S4CORE 107, does not perform necessary authorization checks. A function import could be triggered allowing the attacker to create in-house bank accounts leading to low impact on the confidentiality of the application.
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 confidenceSAP S/4HANA Finance for Advanced Payment Management contains a missing authorization check vulnerability in versions SAPSCORE 128 and S4CORE 107. An attacker can exploit an unprotected function import to create in-house bank accounts without proper authorization, resulting in low confidentiality impact.
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= 107= 128CVSS 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
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 S/4HANA Finance versionExecute SAP transaction code 'SM51' or check system version via 'SAPSystemInfo' to determine if the system runs SAP S/4HANA Finance. Verify the SAPSCORE version number in the system profile or via transaction 'SM37' job logs.Affected if The installed SAPSCORE version equals 128 or the S4CORE version equals 107.
-
Confirm Advanced Payment Management module is activeAccess SAP transaction code 'SPRO' and navigate to SAP Reference IMG. Look for the node 'Financial Supply Chain Management' > 'Payments' > 'Advanced Payment Management' or check if related business function 'FIN_AA_APM' is activated via transaction 'SFW5'.Affected if The Advanced Payment Management module or business function is enabled in the SAP system.
-
Verify authorization for in-house bank account creationUse transaction 'SU53' after attempting to access the function import for in-house bank account creation, or check role authorization via 'PFCG' for roles containing activity '01' (Create) on object 'F_BKPA_BUK' (Bank Account).Affected if Users without proper authorization can access the function import to create in-house bank accounts.
-
Check for unprotected function import accessInspect SAP Gateway activity logs via transaction 'SEGW' or monitor ICF (Internet Communication Framework) logs via 'SICF' for calls to function module '/APM/CL_INHOUSE_BANK_CREATE' or similar function imports in namespace '/APM/'.Affected if The function import for in-house bank account creation accepts requests without proper authorization checks.
A user is affected if their SAP S/4HANA Finance system runs version SAPSCORE 128 or S4CORE 107 with the Advanced Payment Management module enabled, and the function import for creating in-house bank accounts lacks proper authorization controls.
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 dataImplement proper authorization checks on the vulnerable function import to ensure only authorized users can create in-house bank accounts. Apply available SAP security patches for the affected versions.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21736 — 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-2024-21736 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