# CVE-2017-1124: Information disclosure in Maximo Asset Management

> A local attacker can exploit HTTP Header Injection in IBM Maximo Asset Management to obtain sensitive information.

- **Severity:** Low 2.9 (`CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rm2x-c3c3-pwmx

## What is CVE-2017-1124?

CVE-2017-1124 is a low-severity vulnerability in Ibm Maximo Asset Management, published on 7 Mar 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IBM Maximo Asset Management 7.1, 7.5, and 7.6 could allow a local attacker to obtain sensitive information using HTTP Header Injection. IBM Reference #: 1998053.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2017-1124?

It affects 1 product.


Products: Ibm Maximo Asset Management.

## How do I fix CVE-2017-1124?

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

## Is CVE-2017-1124 being exploited?

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

What it is: CVE-2017-1124 is a low-severity vulnerability in Ibm Maximo Asset Management, published on 7 Mar 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-1124 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-2017-1124/ (Markdown: https://insights.sbomify.com/CVE-2017-1124/index.md)
```

## Sources

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

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