dbcve.org
HanaApplication · Sap

CVE-2019-0357

MEDIUM · 6.7 CVSS v3.1 Published 2019-09-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Zero-click

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 · unedited
The administrator of SAP HANA database, before versions 1.0 and 2.0, can misuse HANA to execute commands with operating system "root" privileges.

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 confidence

SAP HANA database administrators can exploit functionality within the database to execute operating system commands with root-level privileges, effectively escalating from database admin rights to full OS root access.

MitigationApply the appropriate SAP security patches for HANA 1.0 and 2.0, and review administrator access controls to ensure only trusted personnel have database admin privileges.

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
HanaApplication
Affected:= 1.0= 2.0

CVSS 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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if SAP HANA is installed
    Run command: hdbversion or check for /hana/shared directory existence. Alternatively, run SQL query: SELECT * FROM M_DATABASE
    Affected if No SAP HANA installation found means not affected
  2. Determine the exact SAP HANA version
    Execute: hdbversion | head -1 or query: SELECT VERSION, COMPONENT_NAME FROM M_COMPONENTS WHERE COMPONENT_NAME = 'HDB'
    Affected if Version falls outside of HANA 1.0 or 2.0 major branches (if your version is 1.0.x or 2.0.x, it may be affected)
  3. Verify database admin privileges
    Connect to HANA database and run: SELECT * FROM GRANTED_ROLES WHERE USER_NAME = CURRENT_USER or check if your user has roles like DATABASE ADMIN or SECURITY ADMIN
    Affected if You are a database admin user in HANA and the version is 1.0 or 2.0, you may be affected
  4. Check for vulnerable OS command execution feature
    Query: SELECT * FROM M_SERVICES where service_type = 'xs' or check if XS Advanced (XSA) is enabled via: xs apps | head or review XSA configuration files in /hana/shared/<SID>/xs/
    Affected if XS Advanced is enabled on HANA 1.0 or 2.0, the privilege escalation vector exists

If you run SAP HANA versions 1.0.x or 2.0.x with XS Advanced enabled and have database admin access, you are affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the appropriate SAP security patches for HANA 1.0 and 2.0, and review administrator access controls to ensure only trusted personnel have database admin privileges.

Fix this in Hana Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-0357 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-0357 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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