# CVE-2012-0195: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script via the display name in IBM Maximo Asset Management components, requiring user interaction to execute.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/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:** 13 Mar 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-r2mg-jvh8-x99r

## What is CVE-2012-0195?

CVE-2012-0195 is a medium-severity cross-site scripting vulnerability in Ibm Maximo Asset Management, published on 13 Mar 2012. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Cross-site scripting (XSS) vulnerability in the Start Center Layout and Configuration component in IBM Maximo Asset Management and Asset Management Essentials 6.2, 7.1, and 7.5; IBM Tivoli Asset Management for IT 6.2, 7.1, and 7.2; IBM Tivoli Service Request Manager 7.1 and 7.2; IBM Maximo Service Desk 6.2; and IBM Tivoli Change and Configuration Management Database (CCMDB) 6.2, 7.1, and 7.2 allows remote attackers to inject arbitrary web script or HTML via the display name.

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

## Which versions are affected by CVE-2012-0195?

It affects 6 products.


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

## How do I fix CVE-2012-0195?

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

## Is CVE-2012-0195 being exploited?

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

What it is: CVE-2012-0195 is a medium-severity cross-site scripting vulnerability in Ibm Maximo Asset Management, published on 13 Mar 2012. 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-2012-0195 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-2012-0195/ (Markdown: https://insights.sbomify.com/CVE-2012-0195/index.md)
```

## Sources

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

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