# CVE-2019-4650: SQL injection in Maximo Asset Management

> Remote attackers can execute SQL injection to view, add, modify, or delete database information in IBM Maximo Asset Management.

- **Severity:** Medium 6.3 (`CVSS:3.0/A:L/AV:N/AC:L/I:L/UI:N/S:U/C:L/PR:L/RL:O/RC:C/E:U`)
- **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 Jun 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-3wp3-9r5c-77fc

## What is CVE-2019-4650?

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

### Official description

IBM Maximo Asset Management 7.6.1.1 is vulnerable to SQL injection. A remote attacker could send specially-crafted SQL statements, which could allow the attacker to view, add, modify or delete information in the back-end database. IBM X-Force ID: 170961.

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

## Which versions are affected by CVE-2019-4650?

It affects 1 product.


Products: Ibm Maximo Asset Management.

## How do I fix CVE-2019-4650?

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

## Is CVE-2019-4650 being exploited?

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

Public exploit code:

- MAximo SQL Injection Time Based - Oracle DB (github_poc): https://github.com/aneeshanilkumar89/Maximo_Sql_Injection-CVE-2019-4650

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

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

## Sources

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

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