How severe is CVE-2019-0350?

CVE-2019-0350 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.

Is CVE-2019-0350 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (61st percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2019-0350?

CVE-2019-0350 primarily affects Sap Hana Database. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2019-0350?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2019-0350 published?

CVE-2019-0350 was published on 2019-11-04 and last updated on 2026-06-17.

CVE-2019-0350

CVE-2019-0350 is a high-severity vulnerability in Sap Hana Database with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v2: 5.0
EPSS exploit prediction: 1% (61st percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Sap Hana Database
Published: 2019-11-04
Last modified: 2026-06-17

Description

SAP HANA Database, versions 1.0, 2.0, allows an unauthorized attacker to send a malformed connection request, which crashes the indexserver of an SAP HANA instance, leading to Denial of Service

Frequently asked questions

What is CVE-2019-0350?: SAP HANA Database, versions 1.0, 2.0, allows an unauthorized attacker to send a malformed connection request, which crashes the indexserver of an SAP HANA instance, leading to Denial of Service
How severe is CVE-2019-0350?: CVE-2019-0350 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2019-0350 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (61st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2019-0350?: CVE-2019-0350 primarily affects Sap Hana Database. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2019-0350?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2019-0350 published?: CVE-2019-0350 was published on 2019-11-04 and last updated on 2026-06-17.

References

Affected products (2)

cpe:2.3:a:sap:hana_database:1.00:*:*:*:*:*:*:*
cpe:2.3:a:sap:hana_database:2.00:*:*:*:*:*:*:*

More vulnerabilities in Sap Hana Database

CVE-2023-40309 — Critical (CVSS 9.8): SAP CommonCryptoLib does not perform necessary authentication checks, which may result in missing or wrong…
CVE-2018-2424 — Critical (CVSS 9.8): SAP UI5 did not validate user input before adding it to the DOM structure. This may lead to malicious user-provided…
CVE-2026-0492 — High (CVSS 8.8): SAP HANA database is vulnerable to privilege escalation allowing an attacker with valid credentials of any user to…
CVE-2023-40308 — High (CVSS 7.5): SAP CommonCryptoLib allows an unauthenticated attacker to craft a request, which when submitted to an open port causes…
CVE-2021-21474 — Medium (CVSS 6.5): SAP HANA Database, versions - 1.0, 2.0, accepts SAML tokens with MD5 digest, an attacker who manages to obtain an…
CVE-2020-26834 — Medium (CVSS 5.4): SAP HANA Database, version - 2.0, does not correctly validate the username when performing SAML bearer token-based user…

All CVEs affecting Sap Hana Database →