# CVE-2016-9977: Auth bypass in Maximo Asset Management

> Remote attackers can hijack user sessions due to improper session invalidation, allowing unauthorized access to other users' accounts.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 7 Jun 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-wgwp-547x-6m92

## What is CVE-2016-9977?

CVE-2016-9977 is a high-severity authentication bypass vulnerability in Ibm Maximo Asset Management, published on 7 Jun 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM Maximo Asset Management 7.1, 7.5, and 7.6 could allow a remote attacker to hijack a user's session, caused by the failure to invalidate an existing session identifier. An attacker could exploit this vulnerability to gain access to another user's session. IBM X-Force ID: 120253.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2016-9977?

It affects 2 products.


Products: Ibm Maximo Asset Management, Ibm Maximo Asset Management Essentials.

## How do I fix CVE-2016-9977?

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

## Is CVE-2016-9977 being exploited?

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

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

## Sources

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

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