dbcve.org
HanaApplication · Sap

CVE-2019-0284

MEDIUM · 6.0 CVSS v3.0 Published 2019-04-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/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
SLD Registration in SAP HANA (fixed in versions 1.0, 2.0) does not sufficiently validate an XML document accepted from an untrusted source. The attacker can call SLDREG with an XML file containing a reference to an XML External Entity (XXE). This can cause SLDREG to, for example, continuously loop, read arbitrary files and even send local files.

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 confidence

SAP HANA SLD Registration utility (SLDREG) does not sufficiently validate XML documents from untrusted sources, allowing XML External Entity (XXE) injection. An attacker can craft malicious XML files containing external entity references to cause denial of service (infinite loops), read arbitrary local files, or exfiltrate data from the server.

MitigationUpdate SAP HANA to versions 1.0 or 2.0 where the vulnerability is fixed. If immediate patching is not possible, disable SLDREG or restrict access to the SLDREG interface to prevent untrusted XML input.

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
None
Availability
High

CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/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 checks

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

  1. Confirm SAP HANA installation
    Run 'HDB version' or check for SAP HANA database processes using 'ps -ef | grep hdb'
    Affected if SAP HANA is not installed on the system
  2. Identify installed SAP HANA version
    Execute 'HDB version' or query the SAP HANA database: SELECT * FROM M_SYSTEM_OVERVIEW WHERE SECTION = 'General' in SQL editor
    Affected if The version is SAP HANA 1.0 or SAP HANA 2.0 (any subversion)
  3. Verify SLDREG component presence
    Check for SLDREG binary or files in SAP HANA installation directory, typically under /usr/sap/<SID>/HDB<instance>/ or search for 'sldreg' using: find /usr/sap -name '*sldreg*' 2>/dev/null
    Affected if SLDREG executable or related files exist on the system
  4. Check SLDREG configuration status
    Examine SAP HANA SLD configuration via SAP HANA cockpit or check configuration files in $DIR_INSTANCE/../sld/ directory for enabled status
    Affected if SLDREG is configured and enabled in the SAP HANA environment

You are affected if SAP HANA versions 1.0 or 2.0 is installed and the SLDREG component is present and enabled on your system.

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

Update SAP HANA to versions 1.0 or 2.0 where the vulnerability is fixed. If immediate patching is not possible, disable SLDREG or restrict access to the SLDREG interface to prevent untrusted XML input.

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

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

Check whether your project pulls in CVE-2019-0284 — 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-0284 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