What is the severity of CVE-2019-4537?

CVE-2019-4537 is classified with a medium severity due to its potential to expose sensitive version information.

How do I fix CVE-2019-4537?

To mitigate CVE-2019-4537, users should upgrade to a secure version of IBM WebSphere Service Registry and Repository above 8.5.

What exploit capabilities does CVE-2019-4537 offer?

CVE-2019-4537 allows attackers to obtain sensitive version information, potentially facilitating further attacks.

Is CVE-2019-4537 specific to certain versions of the software?

Yes, CVE-2019-4537 specifically affects IBM WebSphere Service Registry and Repository version 8.5.

Can CVE-2019-4537 be remotely exploited?

Yes, the vulnerability CVE-2019-4537 can be exploited remotely if an attacker has access to query the affected service.

Vulnerability/
CVE-2019-4537

medium

5.3

25/2/2020

26/2/2020

17/9/2024

CVE-2019-4537

First published: Tue Feb 25 2020(Updated: )

IBM WebSphere Service Registry and Repository 8.5 could allow a user to obtain sensitive version information that could be used in further attacks against the system. IBM X-Force ID: 165593.

Credit: psirt@us.ibm.com

Affected Software	Affected Version	How to fix
IBM WebSphere Service Registry and Repository	=8.5
	<=8.5

Remedy

https://www.ibm.com/support/pages/node/3436359

Never miss a vulnerability like this again

Reference Links

Parent vulnerabilities

(Appears in the following advisories)

IBM-3436359

Frequently Asked Questions

What is the severity of CVE-2019-4537?
CVE-2019-4537 is classified with a medium severity due to its potential to expose sensitive version information.
How do I fix CVE-2019-4537?
To mitigate CVE-2019-4537, users should upgrade to a secure version of IBM WebSphere Service Registry and Repository above 8.5.
What exploit capabilities does CVE-2019-4537 offer?
CVE-2019-4537 allows attackers to obtain sensitive version information, potentially facilitating further attacks.
Is CVE-2019-4537 specific to certain versions of the software?
Yes, CVE-2019-4537 specifically affects IBM WebSphere Service Registry and Repository version 8.5.
Can CVE-2019-4537 be remotely exploited?
Yes, the vulnerability CVE-2019-4537 can be exploited remotely if an attacker has access to query the affected service.

collector/nvd-index
agent/references
agent/type
agent/first-publish-date
agent/remedy
agent/severity
agent/author
agent/description
agent/softwarecombine
collector/ibm-support
source/IBM
agent/software-canonical-lookup
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/event
agent/trending
agent/tags
agent/source
vendor/ibm
canonical/ibm websphere service registry and repository
version/ibm websphere service registry and repository/8.5

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-2019-4537?
CVE-2019-4537 is classified with a medium severity due to its potential to expose sensitive version information.
How do I fix CVE-2019-4537?
To mitigate CVE-2019-4537, users should upgrade to a secure version of IBM WebSphere Service Registry and Repository above 8.5.
What exploit capabilities does CVE-2019-4537 offer?
CVE-2019-4537 allows attackers to obtain sensitive version information, potentially facilitating further attacks.
Is CVE-2019-4537 specific to certain versions of the software?
Yes, CVE-2019-4537 specifically affects IBM WebSphere Service Registry and Repository version 8.5.
Can CVE-2019-4537 be remotely exploited?
Yes, the vulnerability CVE-2019-4537 can be exploited remotely if an attacker has access to query the affected service.