What is the severity of CVE-2016-3639?

CVE-2016-3639 is classified as a low-severity vulnerability that allows exposure of sensitive topology information.

How do I fix CVE-2016-3639?

To mitigate CVE-2016-3639, apply the security patches provided in SAP Security Note 2176128.

Is CVE-2016-3639 exploitable remotely?

Yes, CVE-2016-3639 can be exploited remotely via an unspecified HTTP request.

Which version of SAP HANA DB is affected by CVE-2016-3639?

CVE-2016-3639 affects SAP HANA DB version 1.00.091.00.1418659308.

Vulnerability/
CVE-2016-3639

medium

CWE

200

26/9/2016

6/8/2024

CVE-2016-3639: Infoleak

First published: Mon Sep 26 2016(Updated: )

SAP HANA DB 1.00.091.00.1418659308 allows remote attackers to obtain sensitive topology information via an unspecified HTTP request, aka SAP Security Note 2176128.

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-3639?
CVE-2016-3639 is classified as a low-severity vulnerability that allows exposure of sensitive topology information.
How do I fix CVE-2016-3639?
To mitigate CVE-2016-3639, apply the security patches provided in SAP Security Note 2176128.
What type of information can be disclosed through CVE-2016-3639?
CVE-2016-3639 can allow remote attackers to obtain sensitive topology information from the SAP HANA database.
Is CVE-2016-3639 exploitable remotely?
Yes, CVE-2016-3639 can be exploited remotely via an unspecified HTTP request.
Which version of SAP HANA DB is affected by CVE-2016-3639?
CVE-2016-3639 affects SAP HANA DB version 1.00.091.00.1418659308.

collector/nvd-index
agent/type
agent/references
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/weakness
agent/author
agent/severity
agent/tags
agent/description
agent/first-publish-date
agent/event
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-3639?
CVE-2016-3639 is classified as a low-severity vulnerability that allows exposure of sensitive topology information.
How do I fix CVE-2016-3639?
To mitigate CVE-2016-3639, apply the security patches provided in SAP Security Note 2176128.
What type of information can be disclosed through CVE-2016-3639?
CVE-2016-3639 can allow remote attackers to obtain sensitive topology information from the SAP HANA database.
Is CVE-2016-3639 exploitable remotely?
Yes, CVE-2016-3639 can be exploited remotely via an unspecified HTTP request.
Which version of SAP HANA DB is affected by CVE-2016-3639?
CVE-2016-3639 affects SAP HANA DB version 1.00.091.00.1418659308.

CVE-2016-3639: Infoleak

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-3639?

How do I fix CVE-2016-3639?

What type of information can be disclosed through CVE-2016-3639?

Is CVE-2016-3639 exploitable remotely?

Which version of SAP HANA DB is affected by CVE-2016-3639?

Company

Resources

Contact

Frequently Asked Questions

What is the severity of CVE-2016-3639?

How do I fix CVE-2016-3639?

What type of information can be disclosed through CVE-2016-3639?

Is CVE-2016-3639 exploitable remotely?

Which version of SAP HANA DB is affected by CVE-2016-3639?