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

> Remote attackers can read or modify data in HP Insight Orchestration for Windows via unspecified vectors.

- **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:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 14 Jul 2010
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-8v92-hxr8-99mr

## What is CVE-2010-1965?

CVE-2010-1965 is a high-severity vulnerability in n/a, published on 14 Jul 2010. It can be exploited over the network.

### Official description

Unspecified vulnerability in HP Insight Orchestration for Windows before 6.1 allows remote attackers to read or modify data via unknown vectors.

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

It affects 1 product.


Products: Hp Insight Orchestration.

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

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

## Is CVE-2010-1965 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-4105](https://insights.sbomify.com/CVE-2010-4105/): Unspecified vulnerability in HP Insight Orchestration before 6.2 allows remote attackers to bypass intended access restrictions, and obtain (medium 6.4)
- [CVE-2010-4104](https://insights.sbomify.com/CVE-2010-4104/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-1965 is a high-severity vulnerability in n/a, published on 14 Jul 2010. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2010-1965 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-1965/ (Markdown: https://insights.sbomify.com/CVE-2010-1965/index.md)
```

## Sources

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

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