CVE-2018-2368
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 NetWeaver System Landscape Directory, LM-CORE 7.10, 7.20, 7.30, 7.31, 7.40, does not perform any authentication checks for functionalities that require user identity.
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 NetWeaver System Landscape Directory (SLD) contains a critical authentication bypass vulnerability where certain functionalities that should require user identity verification do not perform any authentication checks. This allows unauthenticated attackers to access sensitive system landscape directory functions that should be restricted to authenticated users.
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= 7.10= 7.20= 7.30= 7.31= 7.40CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Verify SLD component is runningAccess the SLD web interface by navigating to the SLD host (typically port 50000 for HTTP or 50001 for HTTPS) and check if the System Landscape Directory is reachable. For example: http://<host>:50000/sld or https://<host>:50001/sldAffected if The SLD interface is accessible without any authentication prompt.
-
Identify SLD versionLog into the SLD administration console (usually via SAP NetWeaver Administrator or directly through the SLD interface) and locate the version information. The version should be one of: 7.10, 7.20, 7.30, 7.31, or 7.40.Affected if The installed SLD version matches 7.10, 7.20, 7.30, 7.31, or 7.40.
-
Check SLD data supplier configurationIn the SLD administration interface, navigate to the 'Data Suppliers' or 'Technical Configuration' section and examine the configuration of data suppliers (such as the ABAP data supplier or Java data supplier). Look for settings that control authentication requirements.Affected if Data supplier configurations show that authentication is disabled or not enforced for certain SLD functions.
-
Test unauthenticated SLD function accessAttempt to access common SLD API endpoints without providing credentials. Typical endpoints include: /sld/rm/monitoring/data, /sld/TCI/slddb or direct XML API calls. Use a tool like curl to send requests without authentication headers.Affected if Requests to SLD functions return successful responses (HTTP 200) without requiring authentication credentials.
A user is affected if they are running SLD version 7.10, 7.20, 7.30, 7.31, or 7.40 and the SLD interface or specific functions are accessible without authentication.
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.
dbcve · scopedApply the relevant SAP security note/patch for CVE-2018-2368 immediately and review SLD configuration to ensure all protected functionalities enforce proper authentication mechanisms.
SAP NetWeaver 7.40 or later (check SAP Security Notes for exact fixed version)
- Check the SAP Support Portal (support.sap.com) for the latest Security Notes related to CVE-2018-2368
- Identify your current SLD (System Landscape Directory) version via SAP transaction SM37 or SAP MII version checker
- Review available SAP Security Notes for patches - SAP typically releases patches via SAP Note for this type of authentication bypass vulnerability
- If no patch is available, upgrade to a newer SAP NetWeaver version that includes the fix (SAP NetWeaver 7.40 or higher, or the latest available version per SAP's product roadmap)
- After applying patch or upgrade, verify the fix by confirming authentication is now required for all SLD functionalities via transaction RZ70 or SLD administration UI
- Test that all integrated systems (EP, PI, Solution Manager connections) still function correctly post-update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation12.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 $9,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-2368 — 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-2018-2368 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