# CVE-2024-45077: IBM Maximo Asset Management file upload

> Authenticated low-privileged users can upload restricted file types on Windows installations by appending a dot to the filename, potentially leading to code execution.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **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:** 24 Jan 2025
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-m7rj-x62g-9rjj

## What is CVE-2024-45077?

CVE-2024-45077 is a medium-severity vulnerability in Ibm Maximo Asset Management, published on 24 Jan 2025. 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.3 MXAPIASSET API is vulnerable to unrestricted file upload which allows authenticated low privileged user to upload restricted file types with a simple method of adding a dot to the end of the file name if Maximo is installed on Windows operating system.

Weakness: CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program)

## Which versions are affected by CVE-2024-45077?

It affects 1 product.


Products: Ibm Maximo Asset Management.

## How do I fix CVE-2024-45077?

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

## Is CVE-2024-45077 being exploited?

There is no known exploitation of CVE-2024-45077 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-2024-45077 and fix it if it is affected.

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

## Sources

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

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