What is the severity of CVE-2016-6145?

CVE-2016-6145 is classified as a medium severity vulnerability due to its potential for information disclosure.

How do I fix CVE-2016-6145?

To mitigate CVE-2016-6145, ensure that the detailed_error_on_connect option is enabled to prevent different error messages for failed login attempts.

What type of attack is possible with CVE-2016-6145?

CVE-2016-6145 allows remote attackers to enumerate valid usernames and potentially exploit account lockout mechanisms.

Which software versions are affected by CVE-2016-6145?

CVE-2016-6145 specifically affects SAP HANA DB version 1.00.091.00.1418659308.

Can CVE-2016-6145 be exploited remotely?

Yes, CVE-2016-6145 can be exploited remotely by attackers attempting to gather user account information.

Vulnerability/
CVE-2016-6145

medium

5.3

CWE

200

5/8/2016

6/8/2024

CVE-2016-6145: Infoleak

First published: Fri Aug 05 2016(Updated: )

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.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
SAP HANA DB	=1.00.091.00.1418659308

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-6145?
CVE-2016-6145 is classified as a medium severity vulnerability due to its potential for information disclosure.
How do I fix CVE-2016-6145?
To mitigate CVE-2016-6145, ensure that the detailed_error_on_connect option is enabled to prevent different error messages for failed login attempts.
What type of attack is possible with CVE-2016-6145?
CVE-2016-6145 allows remote attackers to enumerate valid usernames and potentially exploit account lockout mechanisms.
Which software versions are affected by CVE-2016-6145?
CVE-2016-6145 specifically affects SAP HANA DB version 1.00.091.00.1418659308.
Can CVE-2016-6145 be exploited remotely?
Yes, CVE-2016-6145 can be exploited remotely by attackers attempting to gather user account information.

collector/nvd-index
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/severity
agent/references
agent/author
agent/weakness
agent/description
agent/event
agent/first-publish-date
agent/tags
agent/source
vendor/sap
canonical/sap hana db
version/sap hana db/1.00.091.00.1418659308

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2016-6145?
CVE-2016-6145 is classified as a medium severity vulnerability due to its potential for information disclosure.
How do I fix CVE-2016-6145?
To mitigate CVE-2016-6145, ensure that the detailed_error_on_connect option is enabled to prevent different error messages for failed login attempts.
What type of attack is possible with CVE-2016-6145?
CVE-2016-6145 allows remote attackers to enumerate valid usernames and potentially exploit account lockout mechanisms.
Which software versions are affected by CVE-2016-6145?
CVE-2016-6145 specifically affects SAP HANA DB version 1.00.091.00.1418659308.
Can CVE-2016-6145 be exploited remotely?
Yes, CVE-2016-6145 can be exploited remotely by attackers attempting to gather user account information.