What is CVE-2016-6145?A medium-severity flaw in Hana DB, explained.
CVE-2016-6145 is a medium-severity flaw (CVSS 5.3) in Hana DB from SAP, published on 5 August 2016. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 1.5%. If you run an affected version, plan in the vendor’s fix.
Published 5 August 2016. Record last updated 12 April 2025. We keep this page's data up to date.
What is CVE-2016-6145? In plain terms.
It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read some data.
The SQL interface in SAP HANA DB 1.00.091.00.1418659308 provides different error messages for failed login attempts depending on whether the username exists and is locked when the detailed_error_on_connect option is not supported or is configured as "False," which allows remote attackers to enumerate database users via a series of login attempts, aka SAP Security Note 2216869.
What kind of flaw is it?
- CWE-200Exposure of Sensitive Information to an Unauthorized Actor
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAnywhere on the internet
- How hard it is to pull offEasy: no special conditions
- Login needed firstNo login needed
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan read some data
Severity vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Is CVE-2016-6145 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 1.5%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
CVE-2016-6145 scores 21. Action: Monitor.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2016-6145 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →How do I fix CVE-2016-6145? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the latest update from the vendor. The references list where the vendor has published details.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
References
5 links- SAP HANA DB 1.00.091.00.1418659308 Information Disclosure (opens in a new tab)packetstormsecurity.com
- Fulldisclosure (opens in a new tab)seclists.org · 2016
- Web page (opens in a new tab)securityfocus.com
- Onapsis Publishes 15 Advisories Sap Hana and Building Components (opens in a new tab)onapsis.com
- Sap Hana User Information Disclosure (opens in a new tab)onapsis.com
Does CVE-2016-6145 affect you? 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
The SQL interface in SAP HANA DB 1.00.091.00.1418659308 provides different error messages for failed login attempts depending on whether the username exists ...
- Matched to
- Hana DB 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.
CVE-2016-6145 is a medium-severity flaw in Hana DB from SAP, published on 5 August 2016. It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read some data.
It scores 5.3 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2016-6145 is 21 out of 100, which is Low. Its action is "Monitor". No sign of exploitation and a low forecast. Patch it in your normal update cycle.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 1.5%. That can change at any time, which is why we keep watching.
For Hana DB from SAP: 1.00.091.00.1418659308.
Install the update the vendor names in its advisory. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.