CVE-2024-42372
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 · uneditedDue to missing authorization check in SAP NetWeaver AS Java (System Landscape Directory) an unauthorized user can read and modify some restricted global SLD configurations causing low impact on confidentiality and 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 · moderate confidenceMissing authorization check in SAP NetWeaver AS Java System Landscape Directory (SLD) allows unauthorized users to read and modify restricted global SLD configurations, resulting in low confidentiality and integrity impact.
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
- 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.
-
Confirm SAP NetWeaver AS Java SLD is installedAccess the SAP NetWeaver Administrator (NWA) or check for SLD service running on the Java stack. Typically accessible via URLs like /sld or through SAP NWA at http://<host>:<port>/nwaAffected if SAP NetWeaver AS Java with System Landscape Directory (SLD) component is present and running
-
Identify the SAP NetWeaver AS Java versionIn SAP NWA, go to Operations > Systems > Overview, or use transaction SM37 and check the JDK version, or access /sap/public/info for version details. Compare against any available SAP security notes for 2024.Affected if The installed SAP NetWeaver AS Java version matches or precedes the patch date for CVE-2024-42372 and has not received the relevant security update
-
Verify SLD configuration endpoint accessibilityAttempt to access the SLD configuration API endpoints without authentication. Common endpoints include /sld/Config or /sld/admin (test via curl or browser: curl -k https://<host>:<port>/sld/Config)Affected if The SLD configuration endpoints respond without requiring authentication or valid credentials
-
Check SLD global configuration access permissionsIn SAP NWA, navigate to Configuration > System Landscape Directory > Global Configuration, or access the SLD Data Supplier configuration. Verify which users or roles can read and modify these settings.Affected if Users without administrative privileges can view or modify restricted global SLD configuration data
-
Review SLD user role assignmentsAccess the SAP NetWeaver AS Java UME (User Management Engine) or use transaction SU01 to review role assignments for SLD-specific roles such as SLD Administrator, SLD Configurator, or SLD Viewer. Check for unexpected or unauthorized role grants.Affected if Unauthorized or non-administrative users have been assigned SLD modification or administrative roles
The environment is affected if SAP NetWeaver AS Java with SLD is running and the SLD configuration endpoints or global configuration data are accessible to unauthorized users without proper role-based access controls applied.
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 patch for CVE-2024-42372 to implement proper authorization checks on SLD configuration endpoints, and verify access controls restrict modifications to authorized administrators only.
- Consultation4.0 h
- Implementation2.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 $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-42372 — 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-42372 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