# CVE-2015-1930: Memory corruption in n/a

> Remote attackers can cause a denial of service via stack-based buffer overflow in IBM Tivoli Storage Manager FastBack server.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jun 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-ccxh-r3rj-ffjf

## What is CVE-2015-1930?

CVE-2015-1930 is a high-severity memory corruption vulnerability in n/a, published on 30 Jun 2015. It can be exploited over the network, with no action from the victim.

### Official description

Stack-based buffer overflow in the server in IBM Tivoli Storage Manager FastBack 6.1 before 6.1.12 allows remote attackers to cause a denial of service (daemon crash) via unspecified vectors, a different vulnerability than CVE-2015-1924, CVE-2015-1925, CVE-2015-1929, CVE-2015-1948, CVE-2015-1953, CVE-2015-1954, CVE-2015-1962, CVE-2015-1963, CVE-2015-1964, and CVE-2015-1965.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2015-1930?

It affects 1 product.


Products: Ibm Tivoli Storage Manager Fastback.

## How do I fix CVE-2015-1930?

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

## Is CVE-2015-1930 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-1930 exists.

Public exploit code:

- IBM Tivoli Storage Manager FastBack Server Opcode 0x534 Denial of Service (metasploit)

## 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-2015-1930 and fix it if it is affected.

What it is: CVE-2015-1930 is a high-severity memory corruption vulnerability in n/a, published on 30 Jun 2015. It can be exploited over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-1930 exists.

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-2015-1930/ (Markdown: https://insights.sbomify.com/CVE-2015-1930/index.md)
```

## Sources

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

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