# CVE-2020-4409: Open redirect in Maximo Asset Management

> Remote attackers can redirect users to malicious sites via tabnabbing, potentially stealing sensitive information or compromising accounts.

- **Severity:** Medium 6.8 (`CVSS:3.0/PR:L/C:N/UI:R/I:H/A:N/AC:L/S:C/AV:N/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Sep 2020
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-mm32-rj9g-9ffc

## What is CVE-2020-4409?

CVE-2020-4409 is a medium-severity vulnerability in Ibm Maximo Asset Management, published on 16 Sep 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

IBM Maximo Asset Management 7.6.0 and 7.6.1 could allow a remote attacker to conduct phishing attacks, using a tabnabbing attack. By persuading a victim to visit a specially-crafted Web site, a remote attacker could exploit this vulnerability to redirect a user to a malicious Web site that would appear to be trusted. This could allow the attacker to obtain highly sensitive information or conduct further attacks against the victim. IBM X-Force ID: 179537.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2020-4409?

It affects 20 products.


Products: Ibm Control Desk, Ibm Maximo Asset Configuration Manager, Ibm Maximo Asset Health Insights, Ibm Maximo Asset Management, Ibm Maximo Asset Management Scheduler, Ibm Maximo Asset Management Scheduler Plus, Ibm Maximo Calibration, Ibm Maximo Enterprise Adapter, Ibm Maximo Equipment Maintenance Assistant, Ibm Maximo for Aviation, Ibm Maximo for Life Sciences, Ibm Maximo for Nuclear Power, Ibm Maximo for Oil and Gas, Ibm Maximo for Service Providers, Ibm Maximo for Transportation, Ibm Maximo for Utilities, Ibm Maximo Linear Asset Manager, Ibm Maximo Network on Blockchain, Ibm Maximo Spatial Asset Management, Ibm Tivoli Integration Composer.

## How do I fix CVE-2020-4409?

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

## Is CVE-2020-4409 being exploited?

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

## Other vulnerabilities in Ibm Maximo Asset Management

- [CVE-2018-2028](https://insights.sbomify.com/CVE-2018-2028/): Open redirect in Maximo Asset Management (medium 6.5)
- [CVE-2019-4644](https://insights.sbomify.com/CVE-2019-4644/): Cross-site scripting in Maximo Asset Management (medium 6.1)
- [CVE-2019-4364](https://insights.sbomify.com/CVE-2019-4364/): Code injection in Maximo Asset Management (medium 5.5)
- [CVE-2021-20559](https://insights.sbomify.com/CVE-2021-20559/): Cross-site scripting in Control Desk (medium 5.4)
- [CVE-2019-4446](https://insights.sbomify.com/CVE-2019-4446/): Missing authorization in Maximo Asset Management (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-4409 and fix it if it is affected.

What it is: CVE-2020-4409 is a medium-severity vulnerability in Ibm Maximo Asset Management, published on 16 Sep 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-4409 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-2020-4409/ (Markdown: https://insights.sbomify.com/CVE-2020-4409/index.md)
```

## Sources

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

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