dbcve.org
Landscape ManagementApplication · Sap

CVE-2019-0261

CRITICAL · 9.8 CVSS v3.0 Published 2019-02-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Under certain circumstances, SAP HANA Extended Application Services, advanced model (XS advanced) does not perform authentication checks properly for XS advanced platform and business users. Fixed in 1.0.97 to 1.0.99 (running on SAP HANA 1 or SAP HANA 2 SPS0 (second S stands for stack)).

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 XS advanced contains an authentication bypass vulnerability where the platform fails to properly validate authentication credentials for both platform and business users under certain conditions. This allows unauthenticated attackers to potentially access sensitive resources and functionality within the SAP HANA environment.

MitigationApply the SAP security patch by upgrading SAP HANA XS advanced to version 1.0.97, 1.0.98, or 1.0.99 (or later) for HANA 1 or HANA 2 SPS0 respectively. Validate the fix by testing authentication flows across all XS advanced applications.

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
Landscape ManagementApplication
Affected:= 3.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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/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 installed SAP Landscape Management version
    Execute command to retrieve SAP Landscape Management version, such as checking the SAP LM installer, viewing version files in the SAP installation directory, or querying the SAP system via transaction code like SLM0 or related system information transactions
    Affected if Version is exactly 3.0 (version 3.0 is affected)
  2. Verify XS Advanced is configured
    Check if SAP HANA XS advanced is enabled in the HANA system by querying the XS advanced status via HANA cockpit, HANA studio, or by checking the xsengine process status
    Affected if XS advanced is active and running in the environment
  3. Confirm HANA database version
    Retrieve the SAP HANA database version using HANA studio, HANA cockpit, or SQL query 'SELECT VERSION FROM SYS.M_DATABASE' or 'SELECT * FROM M_COMPONENT_VERSION'
    Affected if Running HANA 1 or HANA 2 SPS00 with XS advanced enabled, and version is below 1.0.97/1.0.98/1.0.99
  4. Inspect XS advanced authentication configuration
    Review XS advanced xssec and UAA configuration files, typically found in the xssecurity directory or via HANA XS advanced administration console, checking for authentication mechanism settings
    Affected if UAA or xssec authentication is configured but may be bypassed

Environment is affected if running SAP Landscape Management version 3.0 with XS advanced enabled on HANA 1 or HANA 2 SPS00, and the HANA XS advanced version is below 1.0.97/1.0.98/1.0.99.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the SAP security patch by upgrading SAP HANA XS advanced to version 1.0.97, 1.0.98, or 1.0.99 (or later) for HANA 1 or HANA 2 SPS0 respectively. Validate the fix by testing authentication flows across all XS advanced applications.

Recommended fix High confidence

SAP HANA XS advanced version 1.0.97 or higher (1.0.97, 1.0.98, or 1.0.99)

  1. 1. Identify the current SAP HANA XS advanced version by checking the XS advanced platform version
  2. 2. If running SAP HANA 1 or SAP HANA 2 SPS0 with XS advanced version below 1.0.97, plan for upgrade
  3. 3. Upgrade SAP HANA XS advanced to version 1.0.97 or higher (versions 1.0.97, 1.0.98, or 1.0.99 contain the fix)
  4. 4. After upgrade, verify that authentication checks are properly enforced for XS advanced platform and business users
  5. 5. Test that XS advanced applications and services require proper authentication
Caveat Review SAP HANA upgrade guide for potential compatibility impacts when moving to XS advanced 1.0.x versions; test thoroughly in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Landscape Management Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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