CVE-2010-2517: High severity ibm rational clearquest vulnerability
Published Jun 30, 2010
·Updated
Multiple unspecified vulnerabilities in IBM Rational ClearQuest before 7.1.1.02 have unknown impact and attack vectors, as demonstrated by an AppScan report.
Affected Software
35 affected components
IBM Rational ClearQuest<=7.1.1.1
IBM Rational ClearQuest=5.00
IBM Rational ClearQuest=5.20
IBM Rational ClearQuest=6.00
IBM Rational ClearQuest=6.10
IBM Rational ClearQuest=6.12
IBM Rational ClearQuest=6.13
IBM Rational ClearQuest=6.14
IBM Rational ClearQuest=6.15
IBM Rational ClearQuest=6.16
IBM Rational ClearQuest=7.0
IBM Rational ClearQuest=7.0.0.0
IBM Rational ClearQuest=7.0.0.1
IBM Rational ClearQuest=7.0.0.2
IBM Rational ClearQuest=7.0.0.3
IBM Rational ClearQuest=7.0.0.4
IBM Rational ClearQuest=7.0.0.5
IBM Rational ClearQuest=7.0.0.6
IBM Rational ClearQuest=7.0.0.7
IBM Rational ClearQuest=7.0.0.8
IBM Rational ClearQuest=7.0.0.9
IBM Rational ClearQuest=7.0.1
IBM Rational ClearQuest=7.0.1.0
IBM Rational ClearQuest=7.0.1.1
IBM Rational ClearQuest=7.0.1.2
IBM Rational ClearQuest=7.0.1.3
IBM Rational ClearQuest=7.0.1.4
IBM Rational ClearQuest=7.0.1.5
IBM Rational ClearQuest=7.0.1.6
IBM Rational ClearQuest=7.0.1.7
IBM Rational ClearQuest=7.0.1.8
IBM Rational ClearQuest=7.0.1.9
IBM Rational ClearQuest=7.0.2
IBM Rational ClearQuest=2007
IBM Rational ClearQuest=2008
Event History
Jun 30, 2010
CVE Published
via MITRE·06:00 PM
Data Sourced
via MITRE·06:00 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2010-2517?
The severity of CVE-2010-2517 is currently unknown due to unspecified vulnerabilities.
2
How do I fix CVE-2010-2517?
To fix CVE-2010-2517, it is recommended to upgrade IBM Rational ClearQuest to version 7.1.1.02 or later.
3
What versions of IBM Rational ClearQuest are affected by CVE-2010-2517?
CVE-2010-2517 affects IBM Rational ClearQuest versions prior to 7.1.1.02.
4
Can CVE-2010-2517 be exploited remotely?
The attack vectors for CVE-2010-2517 are unknown, so it is unclear if it can be exploited remotely.
5
Is there a public exploit for CVE-2010-2517?
There is currently no public exploit disclosed for CVE-2010-2517.