# CVE-2015-5016: Information disclosure in n/a

> Remote authenticated users can bypass access restrictions to read arbitrary ticket worklog entries in IBM Maximo Asset Management.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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:** 27 Mar 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-p4hm-3m49-2r96

## What is CVE-2015-5016?

CVE-2015-5016 is a medium-severity vulnerability in Ibm Maximo Asset Management, published on 27 Mar 2018. 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; Maximo Asset Management Essentials 7.1 and 7.5; Control Desk 7.5 and 7.6; Tivoli Asset Management for IT 7.1 and 7.2; and certain other IBM products allow remote authenticated users to bypass intended access restrictions and read arbitrary ticket worklog entries via unspecified vectors. IBM X-Force ID: 106460.

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

## Which versions are affected by CVE-2015-5016?

It affects 14 products.


Products: Ibm Change and Configuration Management Database, Ibm Control Desk, Ibm Maximo Asset Management, Ibm Maximo Asset Management Essentials, Ibm Maximo for Aviation, Ibm Maximo for Energy Optimization, 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 Tivoli Asset Management for It, Ibm Tivoli Service Request Manager.

## How do I fix CVE-2015-5016?

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

## Is CVE-2015-5016 being exploited?

There is no known exploitation of CVE-2015-5016 in the wild and no public exploit code.

## Other vulnerabilities in Ibm Maximo Asset Management

- [CVE-2013-3323](https://insights.sbomify.com/CVE-2013-3323/): Privilege escalation in n/a (critical 9.8)
- [CVE-2015-0104](https://insights.sbomify.com/CVE-2015-0104/): Code injection in n/a (high 8.8)
- [CVE-2012-0714](https://insights.sbomify.com/CVE-2012-0714/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2012-2183](https://insights.sbomify.com/CVE-2012-2183/): Auth bypass in n/a (medium 6.8)
- [CVE-2012-2184](https://insights.sbomify.com/CVE-2012-2184/): Auth bypass in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-5016 and fix it if it is affected.

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

## Sources

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

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