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

> Unspecified vulnerability in IBM DB2 Content Manager Toolkit single sign-on allows remote attackers to potentially compromise the system.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 22 Mar 2010
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-mc94-8f9r-f6m9

## What is CVE-2010-1041?

CVE-2010-1041 is a critical vulnerability in n/a, published on 22 Mar 2010. It can be exploited over the network.

### Official description

Unspecified vulnerability in the single sign-on functionality in the Web Services implementation in IBM DB2 Content Manager (CM) Toolkit 8.3 before FP13 on z/OS and DB2 Information Integrator for Content 8.3 before FP13 has unknown impact and remote attack vectors.

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

It affects 1 product.


Products: Ibm Db2 Content Manager.

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

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

## Is CVE-2010-1041 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-1231](https://insights.sbomify.com/CVE-2009-1231/): Other in n/a (critical 10.0)
- [CVE-2008-1681](https://insights.sbomify.com/CVE-2008-1681/): Privilege escalation in n/a (critical 10.0)
- [CVE-2005-3569](https://insights.sbomify.com/CVE-2005-3569/): Denial of service in n/a (medium 5.0)
- [CVE-2005-3568](https://insights.sbomify.com/CVE-2005-3568/): Denial of service in n/a (low 2.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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