CVE-2018-2374
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 · uneditedIn SAP HANA Extended Application Services, 1.0, a controller user who has SpaceAuditor authorization in a specific space could retrieve sensitive application data like service bindings within that space.
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 confidenceIn SAP HANA Extended Application Services (XS) 1.0, the SpaceAuditor role improperly grants access to sensitive application data including service bindings within a space, beyond its intended audit log viewing permissions. This authorization boundary flaw allows users with only SpaceAuditor authorization to retrieve confidential service credentials and binding information that should be restricted.
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= 1.0CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 HANA XS versionRun 'xs version' or check the SAP HANA XS advanced installation to verify the version is exactly 1.0Affected if Version equals 1.0 (exact match per affected versions)
-
Identify users with SpaceAuditor roleQuery the XS advanced UAA or role assignment tables using 'xs get-space-users' or check the UAA role mappings for any user assigned the SpaceAuditor role in any spaceAffected if Any user account is assigned the SpaceAuditor role in the target space
-
Check for service bindings in spacesRun 'xs service-bindings' or query the space metadata to list any applications that have service bindings configuredAffected if Service bindings exist in spaces where SpaceAuditor role is present
-
Inspect SpaceAuditor role permissionsReview the XS advanced role template for SpaceAuditor in the security descriptor files (xs-security.json) to verify if it includes permissions beyond audit log accessAffected if SpaceAuditor role definition includes access to service binding or credential endpoints
-
Verify service credential exposureUsing an account with only SpaceAuditor role, attempt to retrieve service binding details via XS API endpoint '/spaces/{space_guid}/service_bindings'Affected if Service binding credentials are retrievable by SpaceAuditor role users
Environment is affected if running SAP HANA XS 1.0 with SpaceAuditor role assigned to any user in spaces containing service bindings, where that role permits access beyond audit log viewing.
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 dataRestrict the SpaceAuditor role to only allow intended audit log access, and ensure service binding data is not exposed through this authorization level. Apply SAP security notes addressing improper authorization checks in XS advanced.
- 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-2018-2374 — 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-2374 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