dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-44117

MEDIUM · 5.4 CVSS v3.1 Published 2024-09-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
The RFC enabled function module allows a low privileged user to perform various actions, such as modifying the URLs of any user's favourite nodes and workbook ID. There is low impact on 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 confidence

An RFC-enabled function module in an SAP system contains a broken access control vulnerability allowing low-privileged users to modify favourite node URLs and workbook IDs belonging to any user in the system, creating integrity and availability risks.

MitigationImplement proper authorization checks within the RFC function module using appropriate SAP authorization objects to restrict modifications to only authorized users, or disable RFC exposure if not required.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify RFC-enabled function modules related to favourites or workbooks
    Use SAP transaction SE37 or SM37 to list RFC-enabled function modules. Search for modules handling 'FAVOURITE', 'FAVORITE', or 'WORKBOOK' in their names. Check the RFC attributes (transaction SE37 -> Function Module -> Attributes) to confirm RFC is enabled.
    Affected if The function module handling favourite nodes or workbook IDs is exposed via RFC and accessible to low-privileged users
  2. Review authorization objects assigned to the vulnerable function module
    Use transaction SE37 to view the source code of the function module. Check for AUTHORITY-CHECK statements and identify which authorization objects are being used. Use transaction SU21 to review the defined authorization objects for this module.
    Affected if The function module lacks proper AUTHORITY-CHECK statements or uses inadequate authorization objects that do not restrict access to the user's own data only
  3. Verify if guest or low-privileged users can call the RFC function
    Use transaction SU01 to check user roles and profiles. Use transaction PFCG to review role assignments. Attempt to call the RFC function from a low-privileged test user account using transaction SE37 (Test -> Test RFC) or external RFC client.
    Affected if Users with standard or limited roles (without elevated privileges) can successfully execute the RFC function and modify data belonging to other users
  4. Test for cross-user modification capability
    Create or use a low-privileged test user account. Attempt to modify favourite node URLs or workbook IDs belonging to a different user by passing other user IDs in the RFC function parameters. Use transaction DB02 or directly query tables like USR01 or customized favourite tables if accessible.
    Affected if A low-privileged user can successfully modify favourite node URLs or workbook IDs for users other than themselves
  5. Check RFC exposure and network accessibility
    Use transaction SM59 to review RFC destinations and verify if the function module's RFC-enabled group is accessible externally. Check transaction SMOLE to verify if the function is exposed via SAP Gateway or external interfaces.
    Affected if The RFC function module is exposed externally or accessible beyond the trusted internal network without proper restrictions

Your environment is affected if an RFC-enabled function module handling favourite nodes or workbooks lacks proper authorization checks, allowing users with standard privileges to modify data belonging to other users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization checks within the RFC function module using appropriate SAP authorization objects to restrict modifications to only authorized users, or disable RFC exposure if not required.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-44117 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-44117 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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