# CVE-2014-3025: Cross-site scripting in n/a

> Authenticated attackers can inject malicious scripts into IBM Maximo web pages, potentially stealing user data or hijacking sessions.

- **Severity:** Low 3.5 (`AV:N/AC:M/Au:S/C:N/I:P/A:N`)
- **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:** 30 Jul 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3gp4-gxg7-qfjx

## What is CVE-2014-3025?

CVE-2014-3025 is a low-severity cross-site scripting vulnerability in Ibm Maximo Asset Management, published on 30 Jul 2014. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site scripting (XSS) vulnerabilities in IBM Maximo Asset Management 6.2 through 6.2.8, 6.x and 7.1 through 7.1.1.2, and 7.5 through 7.5.0.6; Maximo Asset Management 7.5 through 7.5.0.3 and 7.5.1 through 7.5.1.2 for SmartCloud Control Desk; and Maximo Asset Management 6.2 through 6.2.8, 7.1 through 7.1.1.2, and 7.2 for Tivoli Asset Management for IT and certain other products allow remote authenticated users to inject arbitrary web script or HTML via unspecified input to a .jsp file under webclient/utility/.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2014-3025?

It affects 11 products.


Products: Ibm Maximo Asset Management, Ibm Maximo Asset Management Essentials, Ibm Maximo for Government, Ibm Maximo for Life Sciences, Ibm Maximo for Nuclear Power, Ibm Maximo for Oil and Gas, Ibm Maximo for Transportation, Ibm Maximo for Utilities, Ibm Maximo Service Desk, Ibm Smartcloud Control Desk, Ibm Tivoli It Asset Management for It.

## How do I fix CVE-2014-3025?

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

## Is CVE-2014-3025 being exploited?

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

What it is: CVE-2014-3025 is a low-severity cross-site scripting vulnerability in Ibm Maximo Asset Management, published on 30 Jul 2014. 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-2014-3025 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-2014-3025/ (Markdown: https://insights.sbomify.com/CVE-2014-3025/index.md)
```

## Sources

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

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