CVE-2010-2517 Multiple unspecified vulnerabilities in IBM Rational ClearQuest before 7.1.1.02 have unknown impact and attack vectors, as demonstrated by an AppScan report.
High 7.5
Published
Updated
Check this codebase for CVE-2010-2517 and fix it if it is affected.
What it is: CVE-2010-2517 is a high-severity vulnerability in n/a, published on 30 Jun 2010.
Exploitation: There is no known exploitation of CVE-2010-2517 in the wild and no public exploit code.
Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2010-2517/ (Markdown: https://insights.sbomify.com/CVE-2010-2517/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2010-2517?
CVE-2010-2517 is a high-severity vulnerability in n/a, published on 30 Jun 2010.
Official description
Multiple unspecified vulnerabilities in IBM Rational ClearQuest before 7.1.1.02 have unknown impact and attack vectors, as demonstrated by an AppScan report.
Which versions are affected by CVE-2010-2517?
It affects 1 product.
Products include Ibm Rational Clearquest.
How do I fix CVE-2010-2517?
No fix has been published for CVE-2010-2517 yet. Limit exposure of the affected software until one is available.
Is CVE-2010-2517 being exploited?
There is no known exploitation of CVE-2010-2517 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-7m89-5fj7-x8wv.