What is the severity of CVE-2015-1887?

CVE-2015-1887 is classified as a medium severity vulnerability.

How do I fix CVE-2015-1887?

To fix CVE-2015-1887, upgrade to the patched versions of IBM WebSphere Portal 7.0.0.3, 8.0.0.1 CF18, or 8.5.0 CF07 or later.

What impact does CVE-2015-1887 have on users?

CVE-2015-1887 allows remote attackers to access sensitive information from the Java Content Repository (JCR) of the affected IBM WebSphere Portal versions.

Which versions of IBM WebSphere Portal are affected by CVE-2015-1887?

CVE-2015-1887 affects IBM WebSphere Portal versions 7.0.0 through 7.0.0.2, 8.0.0 before 8.0.0.1, and 8.5.0 before CF06.

Is there a workaround for CVE-2015-1887?

There are no known workarounds for CVE-2015-1887; upgrading to a secure version is the recommended action.

Vulnerability/
CVE-2015-1887

medium

CWE

200

14/7/2015

22/9/2017

CVE-2015-1887: Infoleak

First published: Tue Jul 14 2015(Updated: )

IBM WebSphere Portal 7.0.0 through 7.0.0.2 CF29, 8.0.0 before 8.0.0.1 CF17, and 8.5.0 before CF06 allows remote attackers to obtain sensitive Java Content Repository (JCR) information via a crafted request.

Credit: psirt@us.ibm.com

Affected Software	Affected Version	How to fix
IBM WebSphere Portal	=7.0.0.0
IBM WebSphere Portal	=7.0.0.1
IBM WebSphere Portal	=7.0.0.2
IBM WebSphere Portal	=8.0.0.0
IBM WebSphere Portal	=8.0.0.1
IBM WebSphere Portal	=8.5.0.0

Remedy

http://www-01.ibm.com/support/docview.wss?uid=swg21958024

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2015-1887?
CVE-2015-1887 is classified as a medium severity vulnerability.
How do I fix CVE-2015-1887?
To fix CVE-2015-1887, upgrade to the patched versions of IBM WebSphere Portal 7.0.0.3, 8.0.0.1 CF18, or 8.5.0 CF07 or later.
What impact does CVE-2015-1887 have on users?
CVE-2015-1887 allows remote attackers to access sensitive information from the Java Content Repository (JCR) of the affected IBM WebSphere Portal versions.
Which versions of IBM WebSphere Portal are affected by CVE-2015-1887?
CVE-2015-1887 affects IBM WebSphere Portal versions 7.0.0 through 7.0.0.2, 8.0.0 before 8.0.0.1, and 8.5.0 before CF06.
Is there a workaround for CVE-2015-1887?
There are no known workarounds for CVE-2015-1887; upgrading to a secure version is the recommended action.

agent/severity
agent/references
agent/weakness
agent/author
agent/description
agent/type
agent/event
agent/first-publish-date
agent/softwarecombine
agent/last-modified-date
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
agent/remedy
vendor/ibm
canonical/ibm websphere portal
version/ibm websphere portal/7.0.0.0
version/ibm websphere portal/7.0.0.1
version/ibm websphere portal/7.0.0.2
version/ibm websphere portal/8.0.0.0
version/ibm websphere portal/8.0.0.1
version/ibm websphere portal/8.5.0.0

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-2015-1887?
CVE-2015-1887 is classified as a medium severity vulnerability.
How do I fix CVE-2015-1887?
To fix CVE-2015-1887, upgrade to the patched versions of IBM WebSphere Portal 7.0.0.3, 8.0.0.1 CF18, or 8.5.0 CF07 or later.
What impact does CVE-2015-1887 have on users?
CVE-2015-1887 allows remote attackers to access sensitive information from the Java Content Repository (JCR) of the affected IBM WebSphere Portal versions.
Which versions of IBM WebSphere Portal are affected by CVE-2015-1887?
CVE-2015-1887 affects IBM WebSphere Portal versions 7.0.0 through 7.0.0.2, 8.0.0 before 8.0.0.1, and 8.5.0 before CF06.
Is there a workaround for CVE-2015-1887?
There are no known workarounds for CVE-2015-1887; upgrading to a secure version is the recommended action.