# CVE-2013-4016: SQL injection in n/a

> Authenticated attackers can execute arbitrary SQL commands via Birt reports in IBM Maximo, potentially accessing or modifying database contents.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 May 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vf4v-jx55-rc4w

## What is CVE-2013-4016?

CVE-2013-4016 is a medium-severity SQL injection vulnerability in Ibm Maximo Asset Management, published on 26 May 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SQL injection vulnerability in IBM Maximo Asset Management 7.x before 7.1.1.7 LAFIX.20140319-0837, 7.1.1.11 before IFIX.20140323-0749, 7.1.1.12 before IFIX.20140321-1336, 7.5.x before 7.5.0.3 IFIX027, 7.5.0.4 before IFIX011, and 7.5.0.5 before IFIX006; SmartCloud Control Desk 7.x before 7.5.0.3 and 7.5.1.x before 7.5.1.2; and Tivoli IT Asset Management for IT, Tivoli Service Request Manager, Maximo Service Desk, and Change and Configuration Management Database (CCMDB) 7.x before 7.1.1.7 LAFIX.20140319-0837, 7.1.1.11 before IFIX.20140207-1801, and 7.1.1.12 before IFIX.20140218-1510 allows remote authenticated users to execute arbitrary SQL commands via a Birt report with a WHERE clause in plain text.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 7 products.


Products: Ibm Change and Configuration Management Database, Ibm Maximo Asset Management, Ibm Maximo Service Desk, Ibm Smartcloud Control Desk, Ibm Tivoli Asset Management for It, Ibm Tivoli It Asset Management for It, Ibm Tivoli Service Request Manager.

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

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

## Is CVE-2013-4016 being exploited?

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

## Other vulnerabilities in Ibm Maximo Asset Management

- [CVE-2013-3323](https://insights.sbomify.com/CVE-2013-3323/): Privilege escalation in n/a (critical 9.8)
- [CVE-2015-0104](https://insights.sbomify.com/CVE-2015-0104/): Code injection in n/a (high 8.8)
- [CVE-2012-0714](https://insights.sbomify.com/CVE-2012-0714/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2012-2183](https://insights.sbomify.com/CVE-2012-2183/): Auth bypass in n/a (medium 6.8)
- [CVE-2012-2184](https://insights.sbomify.com/CVE-2012-2184/): Auth bypass in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-4016 is a medium-severity SQL injection vulnerability in Ibm Maximo Asset Management, published on 26 May 2014. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-4016 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-4016/ (Markdown: https://insights.sbomify.com/CVE-2013-4016/index.md)
```

## Sources

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

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