CVE-2024-42373
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 Student Life Cycle Management (SLcM) fails to conduct proper authorization checks for authenticated users, leading to the potential escalation of privileges. On successful exploitation it could allow an attacker to delete non-sensitive report variants that are typically restricted, causing minimal impact on the integrity 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 Student Life Cycle Management (SLcM) contains an authorization flaw where authenticated users can bypass proper authorization checks, potentially allowing privilege escalation. Successful exploitation enables deletion of typically restricted non-sensitive report variants, resulting in minimal integrity 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= 617= 618= 802= 803= 804= 805= 806= 807= 808CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify SAP SLcM installationCheck your SAP system for the presence of SAP Student Life Cycle Management (SLcM) component. This is typically visible in SAP system information or via transaction code SE16N checking table CAPSINSTALLATION or via SAP MYSAPPRODUCTS in the SAP System.Affected if SAP SLcM is not installed in your environment, you are not affected.
-
Determine installed SLcM versionQuery the SAP system for the installed version of SAP Student Life Cycle Management. In SAP systems, this can typically be checked via transaction code SM37, checking the SAP Software Change Register, or using transaction code SPAM to check installed components and their versions.Affected if The installed version matches one of the affected versions: 617, 618, 802, 803, 804, 805, 806, 807, or 808.
-
Verify if report variant deletion feature is accessibleLog in to the SLcM system with a standard user account and attempt to navigate to report variant management areas. In SLcM, report variants are typically managed through transaction code SE71 (SAPscript) or the SLcM reporting module. Try accessing functions that allow deletion of report variants.Affected if Authenticated users can access and delete report variants without proper authorization prompts.
-
Review SLcM authorization role configurationsUsing SAP transaction code PFCG, examine the authorization roles assigned to users in the SLcM system. Check if standard or restricted roles have unauthorized access to delete operations on report variants. Look for authorization objects S_RS_REPO or similar in the role definitions.Affected if Users have roles that grant delete access to report variants without proper restrictions.
Your environment is affected if SAP SLcM is installed and the installed version matches 617, 618, 802, 803, 804, 805, 806, 807, or 808, and users can delete report variants without proper authorization checks.
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 SAP security patches for this authorization vulnerability and review SLcM authorization roles to ensure proper access controls are enforced for report variant deletion operations.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-42373 — 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-42373 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