# CVE-2013-0484: Denial of service in n/a

> Remote attackers can crash the IBM Cognos TM1 server daemon via a specific API call, causing a denial of service.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jun 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-4xm6-968w-v5q8

## What is CVE-2013-0484?

CVE-2013-0484 is a medium-severity denial of service vulnerability in n/a, published on 19 Jun 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The server process in IBM Cognos TM1 10.1.x before 10.1.1 FP1 allows remote attackers to cause a denial of service (daemon crash) via an undocumented API call that triggers the transmission of unexpected data.

## Which versions are affected by CVE-2013-0484?

It affects 1 product.


Products: Ibm Cognos Tm1.

## How do I fix CVE-2013-0484?

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

## Is CVE-2013-0484 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-0202](https://insights.sbomify.com/CVE-2012-0202/): Memory corruption in n/a (critical 10.0)
- [CVE-2017-1506](https://insights.sbomify.com/CVE-2017-1506/): Cross-site scripting in Cognos TM1 (medium 6.1)
- [CVE-2014-0877](https://insights.sbomify.com/CVE-2014-0877/): Auth bypass in n/a (medium 5.0)
- [CVE-2016-0381](https://insights.sbomify.com/CVE-2016-0381/): Denial of service in n/a (medium 4.3)
- [CVE-2012-6350](https://insights.sbomify.com/CVE-2012-6350/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-0484 and fix it if it is affected.

What it is: CVE-2013-0484 is a medium-severity denial of service vulnerability in n/a, published on 19 Jun 2013. 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-2013-0484 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-2013-0484/ (Markdown: https://insights.sbomify.com/CVE-2013-0484/index.md)
```

## Sources

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

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