CVE-2018-2378
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, unauthorized users can read statistical data about deployed applications including resource consumption.
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 confidenceThis is an information disclosure vulnerability in SAP HANA Extended Application Services (XS) 1.0 where unauthenticated or unauthorized users can read statistical data about deployed applications, including resource consumption metrics. The flaw allows exposure of sensitive operational data without proper authentication controls.
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.
-
Identify SAP HANA XS installationRun 'HDB version' or check SAP HANA installation directory for xs folder structure. Query the database: SELECT * FROM M_COMPONENTS WHERE COMPONENT LIKE '%XS%';Affected if Version shown is exactly 1.0 for the XS component
-
Verify XS core HTTP server is runningCheck XS processes: ps -ef | grep xs or query SAP HANA management views: SELECT * FROM M_SERVICES WHERE SERVICE_NAME = 'xs';Affected if XS core service is running (required for this attack surface)
-
Identify exposed XS statistical endpointsQuery XS routes and exposed URLs via: SELECT * FROM _SYS_XS.RUNTIME_APPLICATIONS WHERE application_type = 'JAVASCRIPT'; or check /sap/hana/xs/admin/ endpointsAffected if XS statistical or admin endpoints are exposed via HTTP/HTTPS
-
Test unauthenticated access to statisticsAttempt curl http(s)://<host>:8000/sap/hana/xs/admin/ or /sap/hana/xs/stats/ endpoints without providing credentialsAffected if Response returns statistical data without requiring authentication (200 OK with data)
-
Check XS application authentication configurationExamine .xsaccess or .xsapp files in the /sap/hana/xs/admin/ directory, or query: SELECT * FROM _SYS_XS.ACTIVE_APPLICATIONS WHERE require_authentication = false;Affected if Authentication is disabled or missing for statistical endpoints (require_authentication = false or not set)
A user is affected if SAP HANA XS 1.0 is running with unauthenticated or improperly authorized access to statistical data endpoints that expose application resource metrics.
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 dataImplement proper authentication and authorization checks for all statistical data endpoints in SAP HANA XS 1.0 to ensure only authorized users can access application statistics and resource consumption data.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-2378 — 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-2378 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