CVE-2018-2373
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 · uneditedUnder certain circumstances, a specific endpoint of the Controller's API could be misused by unauthenticated users to execute SQL statements that deliver information about system configuration in SAP HANA Extended Application Services, 1.0.
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 confidenceAn unauthenticated SQL injection vulnerability in the Controller API endpoint of SAP HANA Extended Application Services (XS) 1.0 allows remote attackers to execute arbitrary SQL statements and retrieve system configuration information without any authentication credentials.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/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 installationCheck the SAP HANA system for the presence of SAP HANA Extended Application Services (XS) 1.0 by querying the SAP HANA instance metadata or checking installed packages: SELECT * FROM M_COMPONENTS WHERE COMPONENT_NAME LIKE '%XS%';Affected if The component version returned is exactly 1.0 (XS 1.0)
-
Verify Controller API endpoint exposureConfirm the SAP HANA XS Controller API endpoint is network-accessible. This endpoint is typically exposed on port 80/443 under paths like /sap/hana/xs/controller/ or similar XS routing paths. Check your web server or SAP HANA XS configuration files for exposed routes.Affected if The Controller API endpoint is externally accessible without authentication requirements configured at the network or application layer
-
Check for unauthenticated access to Controller APIAttempt a simple unauthenticated HTTP request to the Controller API endpoint (e.g., GET /sap/hana/xs/controller/) from an untrusted network perspective. If the system returns a response rather than rejecting the request with authentication challenges, the endpoint may be exposed.Affected if The endpoint responds to unauthenticated requests with valid API data or configuration information instead of requiring authentication
-
Review XS security configurationInspect the SAP HANA XS configuration files (xsconfig.ini, xssec.properties) and the xsengine process configuration for authentication enforcement on the Controller API. Look for settings that disable authentication for the controller endpoint.Affected if Authentication is disabled or not enforced on the Controller API endpoint in the XS configuration
A system is affected if it runs SAP HANA XS 1.0 with the Controller API endpoint exposed and unauthenticated access permitted.
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 the relevant SAP security patch for CVE-2018-2373 and implement network-level access controls to restrict exposure of the vulnerable Controller API endpoint until the patch is deployed.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-2373 — 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-2373 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