CVE-2013-5422: Infoleak
Published Dec 19, 2013
·Updated
The Web Client in IBM Rational ClearQuest 7.1 through 7.1.2.12, 8.0.0.x before 8.0.0.9, and 8.0.1.x before 8.0.1.2, when a multi-database dataset exists, allows remote attackers to read database names via unspecified vectors.
Affected Software
36 affected components
IBM Rational ClearCase=7.1
IBM Rational ClearCase=7.1.0.1
IBM Rational ClearCase=7.1.0.2
IBM Rational ClearCase=7.1.1
IBM Rational ClearCase=7.1.1.1
IBM Rational ClearCase=7.1.1.2
IBM Rational ClearCase=7.1.1.3
IBM Rational ClearCase=7.1.1.4
IBM Rational ClearCase=7.1.1.5
IBM Rational ClearCase=7.1.1.6
IBM Rational ClearCase=7.1.1.7
IBM Rational ClearCase=7.1.1.8
IBM Rational ClearCase=7.1.1.9
IBM Rational ClearCase=7.1.2
IBM Rational ClearCase=7.1.2.1
IBM Rational ClearCase=7.1.2.2
IBM Rational ClearCase=7.1.2.3
IBM Rational ClearCase=7.1.2.4
IBM Rational ClearCase=7.1.2.5
IBM Rational ClearCase=7.1.2.6
IBM Rational ClearCase=7.1.2.7
IBM Rational ClearCase=7.1.2.9
IBM Rational ClearCase=7.1.2.10
IBM Rational ClearCase=7.1.2.11
IBM Rational ClearCase=7.1.2.12
IBM Rational ClearCase=8.0
IBM Rational ClearCase=8.0.0.1
IBM Rational ClearCase=8.0.0.2
IBM Rational ClearCase=8.0.0.3
IBM Rational ClearCase=8.0.0.4
IBM Rational ClearCase=8.0.0.5
IBM Rational ClearCase=8.0.0.6
IBM Rational ClearCase=8.0.0.7
IBM Rational ClearCase=8.0.0.8
IBM Rational ClearCase=8.0.1
IBM Rational ClearCase=8.0.1.1
Event History
Dec 19, 2013
CVE Published
via MITRE·10:00 PM
Data Sourced
via MITRE·10:00 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2013-5422?
CVE-2013-5422 has been classified as a moderate severity vulnerability.
2
How do I fix CVE-2013-5422?
To fix CVE-2013-5422, upgrade to IBM Rational ClearQuest versions 8.0.0.9, 8.0.1.2, or later.
3
What versions of IBM Rational ClearQuest are affected by CVE-2013-5422?
CVE-2013-5422 affects IBM Rational ClearQuest versions 7.1 to 7.1.2.12 and 8.0.0.x before 8.0.0.9.
4
Can CVE-2013-5422 allow unauthorized access to data?
Yes, CVE-2013-5422 allows remote attackers to read database names, potentially leading to unauthorized access.
5
Is there a workaround for CVE-2013-5422?
A recommended workaround for CVE-2013-5422 is to restrict access to the affected databases until an upgrade can be performed.