# CVE-2013-4013: Information disclosure in n/a

> Remote attackers can obtain sensitive information from IBM Maximo Asset Management via unspecified vectors.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 1 Oct 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-cfhx-6jmm-q25v

## What is CVE-2013-4013?

CVE-2013-4013 is a medium-severity vulnerability in Ibm Maximo Asset Management, published on 1 Oct 2013. It can be exploited over the network.

### Official description

IBM Maximo Asset Management 6.2 through 6.2.8, 7.1 through 7.1.1.12, and 7.5 before 7.5.0.2 allows remote attackers to obtain sensitive information via unspecified vectors.

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

It affects 1 product.


Products: Ibm Maximo Asset Management.

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

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

## Is CVE-2013-4013 being exploited?

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

## Other vulnerabilities in Ibm Maximo Asset Management

- [CVE-2020-4493](https://insights.sbomify.com/CVE-2020-4493/): Auth bypass in Maximo Asset Management (critical 9.8)
- [CVE-2017-1175](https://insights.sbomify.com/CVE-2017-1175/): SQL injection in Maximo Asset Management (critical 9.8)
- [CVE-2020-4521](https://insights.sbomify.com/CVE-2020-4521/): Deserialization in Maximo Asset Management (high 8.8)
- [CVE-2018-1524](https://insights.sbomify.com/CVE-2018-1524/): Hardcoded credentials in Maximo Asset Management (high 8.8)
- [CVE-2018-1414](https://insights.sbomify.com/CVE-2018-1414/): SQL injection in Maximo Asset Management (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-4013 is a medium-severity vulnerability in Ibm Maximo Asset Management, published on 1 Oct 2013. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2013-4013 in the wild and no public exploit code.

Affected product: Ibm Maximo Asset Management. 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-4013/ (Markdown: https://insights.sbomify.com/CVE-2013-4013/index.md)
```

## Sources

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

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