# CVE-2010-3758: Memory corruption in n/a

> Remote attackers can execute arbitrary code on IBM Tivoli Storage Manager FastBack Server via stack-based buffer overflows in multiple functions.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Oct 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5mvg-7mqq-mfx7

## What is CVE-2010-3758?

CVE-2010-3758 is a critical memory corruption vulnerability in n/a, published on 5 Oct 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple stack-based buffer overflows in FastBackServer.exe in the Server in IBM Tivoli Storage Manager (TSM) FastBack 5.5.0.0 through 5.5.6.0 and 6.1.0.0 through 6.1.0.1 allow remote attackers to execute arbitrary code via vectors involving the (1) AGI_SendToLog (aka _SendToLog) function; the (2) group, (3) workgroup, or (4) domain name field to the USER_S_AddADGroup function; the (5) user_path variable to the FXCLI_checkIndexDBLocation function; or (6) the _AGI_S_ActivateLTScriptReply (aka ActivateLTScriptReply) function. NOTE: this might overlap CVE-2010-3059.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Ibm Tivoli Storage Manager Fastback.

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

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

## Is CVE-2010-3758 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-4931](https://insights.sbomify.com/CVE-2015-4931/): Memory corruption in n/a (critical 10.0)
- [CVE-2015-4932](https://insights.sbomify.com/CVE-2015-4932/): Memory corruption in n/a (critical 10.0)
- [CVE-2015-4933](https://insights.sbomify.com/CVE-2015-4933/): Memory corruption in n/a (critical 10.0)
- [CVE-2015-4934](https://insights.sbomify.com/CVE-2015-4934/): Memory corruption in n/a (critical 10.0)
- [CVE-2015-4935](https://insights.sbomify.com/CVE-2015-4935/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-3758 is a critical memory corruption vulnerability in n/a, published on 5 Oct 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-3758 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-3758/ (Markdown: https://insights.sbomify.com/CVE-2010-3758/index.md)
```

## Sources

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

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