# CVE-2013-0501: Other in n/a

> Remote attackers can execute arbitrary code or read files via a crafted website exploiting an ActiveX control in IBM Cognos Disclosure Management.

- **Severity:** Critical 9.3 (`AV:N/AC:M/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Apr 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-xrq4-7fj4-886m

## What is CVE-2013-0501?

CVE-2013-0501 is a critical vulnerability in n/a, published on 12 Apr 2013. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The EdrawSoft EDOFFICE.EDOfficeCtrl.1 ActiveX control, as used in Edraw Office Viewer Component, the client in IBM Cognos Disclosure Management (CDM) 10.2.0, and other products, allows remote attackers to read arbitrary files, or download an arbitrary program onto a client machine and execute this program, via a crafted web site.

Weakness: CWE-264

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

It affects 1 product.


Products: Ibm Cognos Disclosure Management.

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

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

## Is CVE-2013-0501 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-5014](https://insights.sbomify.com/CVE-2015-5014/): Other in n/a (critical 9.3)
- [CVE-2016-6077](https://insights.sbomify.com/CVE-2016-6077/): Command injection in Cognos Disclosure Management (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-0501 is a critical vulnerability in n/a, published on 12 Apr 2013. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2013-0501 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-0501/ (Markdown: https://insights.sbomify.com/CVE-2013-0501/index.md)
```

## Sources

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

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