Hana Database vulnerabilitiesRanked by how likely they are to be used.
Hana Database is made by SAP. We track 7 published vulnerabilities in it, across 3 versions. None of them is on the list of flaws known to be exploited today. If you run Hana Database, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Hana Database vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Hana Database's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Hana Database flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 2.4%CVE-2018-2424High
SAP UI5 did not validate user input before adding it to the DOM structure.
- 1.3%CVE-2017-16687Medium
The user self-service tools of SAP HANA extended application services, classic user self-service, a part of SAP HANA Database versions 1.00 and 2.00, can be misused to enumerate valid and invalid user accounts.
- 1.1%CVE-2019-0350High
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
- 0.9%CVE-2023-40309Critical
SAP CommonCryptoLib does not perform necessary authentication checks, which may result in missing or wrong authorization checks for an authenticated user, resulting in escalation of privileges.
- 0.8%CVE-2023-40308High
SAP CommonCryptoLib allows an unauthenticated attacker to craft a request, which when submitted to an open port causes a memory corruption error in a library which in turn causes the target component to crash making...
- 0.7%CVE-2021-21474Medium
SAP HANA Database, versions - 1.0, 2.0, accepts SAML tokens with MD5 digest, an attacker who manages to obtain an MD5-digest signed SAML Assertion issued for an SAP HANA instance might be able to tamper with it and...
- 0.7%CVE-2020-26834Medium
SAP HANA Database, version - 2.0, does not correctly validate the username when performing SAML bearer token-based user authentication.
Running Hana Database? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
SAP UI5 did not validate user input before adding it to the DOM structure. This may lead to malicious user-provided JavaScript code being added to the DOM that could steal user information. Software components affected are: SAP Hana Database 1.00, 2.00; SAP UI5 1.00; SAP UI5 (Java) 7.30, 7.31, 7.40, 7,50; SAP UI 7.40, 7.50, 7.51, 7.52, and version 2.0 of SAP UI for SAP NetWeaver 7.00
- Matched to
- Hana Database on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 7 published vulnerabilities listed under the name Hana Database, across 3 versions.
None of Hana Database's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Hana Database. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.