CVE-2024-24739
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 Bank Account Management (BAM) allows an authenticated user with restricted access to use functions which can result in escalation of privileges with low impact on confidentiality, integrity and availability 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 · moderate confidenceSAP Bank Account Management contains a privilege escalation vulnerability where an authenticated user with restricted access can bypass authorization controls to access functions beyond their intended permission level, leading to unauthorized elevation of privileges within the application.
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= s4core_100= s4core_101= sap_fin_618= sap_fin_730CVSS 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
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 Bank Account Management versionIn SAP transaction SM37, check the SAP_BAM component version or query system table CRMD_ORDER for BAM module version. Alternatively, use SAP transaction SAINT to view installed software components and locate SAP_BAM or S4CORE/SAP_FIN version numbers.Affected if The installed version matches s4core_100, s4core_101, sap_fin_618, or sap_fin_730.
-
Confirm SAP BAM application is activeCheck if SAP Bank Account Management is deployed by querying transaction SE11 for table Tadir with object class = 'BAM' or check transaction SICF for service path /sap/bam being active.Affected if SAP BAM services are active in the SAP system.
-
Review user role assignments for restricted usersUse transaction SUIM to query user role assignments. Identify users assigned restricted or limited roles within the Bank Account Management module.Affected if Users with restricted BAM roles exist in the system.
-
Check for privileged function access pathsExamine SAP transaction authorizations using transaction SU24 or auth trace (transaction ST01) to identify which functions restricted users can invoke versus what they should be permitted to access.Affected if Restricted users have access to functions beyond their assigned authorization scope.
The environment is affected if SAP Bank Account Management is running any of the listed versions (s4core_100, s4core_101, sap_fin_618, sap_fin_730) and restricted users can potentially invoke privileged functions beyond their authorization level.
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 role-based access control (RBAC) enforcement in SAP BAM and review user authorizations to ensure restricted users cannot invoke privileged functions; apply SAP security notes/patches for BAM.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24739 — 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-24739 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