CVE-2013-6735: Medium severity IBM WebSphere Portal vulnerability

Published Dec 22, 2013
·
Updated

IBM WebSphere Portal 6.0.0.x through 6.0.0.1, 6.0.1.x through 6.0.1.7, 6.1.0.x through 6.1.0.6 CF27, 6.1.5.x through 6.1.5.3 CF27, 7.0.0.x through 7.0.0.2 CF26, and 8.0.0.x through 8.0.0.1 CF08 allows remote attackers to obtain sensitive Java Content Repository (JCR) information via a modified Web Content Manager (WCM) URL.

Affected Software

26 affected components
IBM WebSphere Portal=6.0.0.0
IBM WebSphere Portal=6.0.0.1
IBM WebSphere Portal=6.0.1.0
IBM WebSphere Portal=6.0.1.1
IBM WebSphere Portal=6.0.1.2
IBM WebSphere Portal=6.0.1.3
IBM WebSphere Portal=6.0.1.4
IBM WebSphere Portal=6.0.1.5
IBM WebSphere Portal=6.0.1.6
IBM WebSphere Portal=6.0.1.7
IBM WebSphere Portal=6.1.0.0
IBM WebSphere Portal=6.1.0.1
IBM WebSphere Portal=6.1.0.2
IBM WebSphere Portal=6.1.0.3
IBM WebSphere Portal=6.1.0.4
IBM WebSphere Portal=6.1.0.5
IBM WebSphere Portal=6.1.0.6
IBM WebSphere Portal=6.1.5.0
IBM WebSphere Portal=6.1.5.1
IBM WebSphere Portal=6.1.5.2
IBM WebSphere Portal=6.1.5.3
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

Event History

Dec 22, 2013
CVE Published
via MITRE·03:00 PM
Data Sourced
via MITRE·03:00 PM
Description
Data Sourced
via NVD·03:16 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2013-6735?

CVE-2013-6735 has a medium severity score due to the potential for remote attackers to access sensitive information.

2

How do I fix CVE-2013-6735?

To fix CVE-2013-6735, you should apply the latest security patches provided by IBM for your version of WebSphere Portal.

3

What versions of IBM WebSphere Portal are affected by CVE-2013-6735?

CVE-2013-6735 affects IBM WebSphere Portal versions 6.0.0.x through 8.0.0.1.

4

What are the potential risks of CVE-2013-6735?

The risks of CVE-2013-6735 include unauthorized access to sensitive Java Content Repository information.

5

Is there a workaround for CVE-2013-6735 if I cannot apply a patch immediately?

A potential workaround for CVE-2013-6735 is to restrict access to the affected components to trusted users only.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203