# CVE-2010-0937: Other in n/a

> Multiple unspecified vulnerabilities in Visualization Library allow attackers to potentially compromise the application, requiring an upgrade to a fixed version.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 8 Mar 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-49fq-jf7g-7fxv

## What is CVE-2010-0937?

CVE-2010-0937 is a high-severity vulnerability in n/a, published on 8 Mar 2010. 

### Official description

Multiple unspecified vulnerabilities in Visualization Library before 2009.08.812 have unknown impact and attack vectors.

## Which versions are affected by CVE-2010-0937?

It affects 1 product.


Products: Visualizationlibrary Visualization Library.

## How do I fix CVE-2010-0937?

No fix has been published for CVE-2010-0937 yet. Limit exposure of the affected software until one is available.

## Is CVE-2010-0937 being exploited?

There is no known exploitation of CVE-2010-0937 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2010-0994](https://insights.sbomify.com/CVE-2010-0994/): Memory corruption in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-0937 and fix it if it is affected.

What it is: CVE-2010-0937 is a high-severity vulnerability in n/a, published on 8 Mar 2010. 
Exploitation: There is no known exploitation of CVE-2010-0937 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-0937/ (Markdown: https://insights.sbomify.com/CVE-2010-0937/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2010-0937
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2010-0937
- OSV: https://osv.dev/vulnerability/CVE-2010-0937

---
From sbomify Insights: https://insights.sbomify.com/CVE-2010-0937/
Summaries are generated and may contain mistakes; the official description above is the record.