First published: Wed Dec 24 2014(Updated: )
IBM WebSphere Service Registry and Repository (WSRR) 7.0.x before 7.0.0.5 and 7.5.x before 7.5.0.3 does not perform access-control checks for depth-0 retrieve operations, which allows remote authenticated users to obtain sensitive information via unspecified vectors.
Credit: psirt@us.ibm.com
Affected Software | Affected Version | How to fix |
---|---|---|
IBM WebSphere Service Registry and Repository | =7.0.0 | |
IBM WebSphere Service Registry and Repository | =7.0.0.1 | |
IBM WebSphere Service Registry and Repository | =7.0.0.2 | |
IBM WebSphere Service Registry and Repository | =7.0.0.3 | |
IBM WebSphere Service Registry and Repository | =7.0.0.4 | |
IBM WebSphere Service Registry and Repository | =7.5.0.0 | |
IBM WebSphere Service Registry and Repository | =7.5.0.1 | |
IBM WebSphere Service Registry and Repository | =7.5.0.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2014-6177 is considered medium due to its potential to expose sensitive information to remote authenticated users.
To fix CVE-2014-6177, update IBM WebSphere Service Registry and Repository to version 7.0.0.5 or 7.5.0.3 or later.
CVE-2014-6177 affects IBM WebSphere Service Registry and Repository versions 7.0.0 to 7.0.0.4 and 7.5.0.0 to 7.5.0.2.
CVE-2014-6177 can potentially expose sensitive configuration and operational data from the IBM WebSphere Service Registry and Repository.
No, CVE-2014-6177 does not involve an authentication bypass but rather lacks adequate access-control checks for certain operations.