dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-28167

MEDIUM · 6.5 CVSS v3.1 Published 2024-04-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/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
SAP Group Reporting Data Collection does not perform necessary authorization checks for an authenticated user, resulting in escalation of privileges. On successful exploitation, specific data can be changed via the Enter Package Data app although the user does not have sufficient authorization causing high impact on Integrity of the appliction.

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

SAP Group Reporting Data Collection contains an insecure direct object reference or authorization bypass vulnerability in the Enter Package Data application. An authenticated user with low-level privileges can access functionality intended for higher-privileged users, allowing unauthorized modification of data that should be protected by the application's authorization model.

MitigationImplement proper role-based access control (RBAC) enforcement in the Enter Package Data app and review/restrict user roles to ensure least-privilege principles. Apply SAP security notes and validate authorization checks are performed before any data modification operations.

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
High
Availability
None

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

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

  1. Identify SAP Group Reporting Data Collection installation
    Check your SAP system for installed software component SAP Group Reporting Data Collection. Use transaction code SE16 or SM37 to query installed software components, or check SAP LMDB (Landscape Management Database).
    Affected if The software component SAP Group Reporting Data Collection is present in the system
  2. Determine installed version
    Use SAP transaction code SM21 or check the installed software version through SAP Solution Manager. Compare your installed version against any SAP security notes for CVE-2024-28167 that specify version ranges.
    Affected if Version is within an affected range or cannot be verified against SAP security patches
  3. Verify Enter Package Data application is configured
    Check if the Enter Package Data application (typically accessed via SAP Fiori launchpad or transaction code associated with Group Reporting) is enabled in your SAP system. Use transaction code /n/GR/PCM_UI or check application configuration.
    Affected if Enter Package Data application is active and accessible to users
  4. Review user role assignments
    Use transaction code PFCG or SU01 to examine user roles. Identify users assigned to low-privilege roles in the Group Reporting module. Check if any low-level roles have access to data modification functions.
    Affected if Low-privilege users exist who should not have elevated access but are assigned to Group Reporting roles
  5. Test authorization boundaries
    Log in with a low-privilege user account that has basic Group Reporting access. Attempt to access Enter Package Data functions that should be restricted to higher-privileged roles. Compare intended role permissions against actual accessible functions.
    Affected if Low-privilege users can access or modify data that should require higher-privilege roles

The environment is affected if SAP Group Reporting Data Collection with the Enter Package Data application is installed and low-privilege users can access functions reserved for higher-privileged roles.

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 role-based access control (RBAC) enforcement in the Enter Package Data app and review/restrict user roles to ensure least-privilege principles. Apply SAP security notes and validate authorization checks are performed before any data modification operations.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-28167 — 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-28167 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