CVE-2019-0363
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 · uneditedAttackers may misuse an HTTP/REST endpoint of SAP HANA Extended Application Services (Advanced model), before version 1.0.118, to overload the server or retrieve information about internal network ports.
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 confidenceThe vulnerability allows misuse of an HTTP/REST endpoint in SAP HANA Extended Application Services (Advanced model) versions prior to 1.0.118, enabling attackers to overload the server through DoS attacks and gather information about internal network ports for further reconnaissance.
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.0.118CVSS 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
- Low
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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.
-
Identify SAP HANA XS Advanced versionQuery the SAP HANA system for the installed version of SAP HANA Extended Application Services (Advanced model). This is typically available through SAP HANA administration tools or by querying the system landscape. Compare the installed version against the affected range (versions prior to 1.0.118).Affected if The installed version of SAP HANA Extended Application Services (Advanced model) is below 1.0.118
-
Confirm HTTP/REST endpoint presenceInspect the SAP HANA XS Advanced configuration to determine if HTTP/REST endpoints are enabled. Review the xsuaa or webdispat service configuration files and routing definitions for the Advanced model applications.Affected if HTTP/REST endpoints are enabled and accessible in the SAP HANA XS Advanced environment
-
Check endpoint exposureReview the routing and access policies configured for the SAP HANA XS Advanced model applications. Examine the xs-security.json or similar configuration files that define endpoint accessibility and authentication requirements.Affected if The vulnerable HTTP/REST endpoint is exposed without proper authentication or rate limiting controls
-
Audit network accessibilityVerify which network interfaces and ports the SAP HANA XS Advanced services are bound to. Check if the HTTP/REST endpoint is reachable from internal or external network segments.Affected if The HTTP/REST endpoint is reachable from network segments beyond the intended trust boundary
A user is affected if SAP HANA Extended Application Services (Advanced model) is installed at a version below 1.0.118 AND the HTTP/REST endpoint is enabled and accessible in their environment.
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 data1.0.118
Upgrade SAP HANA Extended Application Services (Advanced model) to version 1.0.118 or later to remediate this vulnerability.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0363 — 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-2019-0363 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