# CVE-2019-4546: Privilege escalation in Maximo Health- Safety and Environment Manager

> Installing IBM Maximo HSE Manager grants users unauthorized additional privileges, allowing privilege escalation within the application.

- **Severity:** Medium 5.4 (`CVSS:3.0/I:L/PR:L/S:U/AC:L/A:N/UI:N/C:L/AV:N/RC:C/RL:O/E:U`)
- **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:** 28 Oct 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-33pq-4v9h-pchm

## What is CVE-2019-4546?

CVE-2019-4546 is a medium-severity vulnerability in IBM Maximo Health- Safety and Environment Manager, published on 28 Oct 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

After installing the IBM Maximo Health- Safety and Environment Manager 7.6.1, a user is granted additional privileges that they are not normally allowed to access. IBM X-Force ID: 165948.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2019-4546?

It affects 2 products.


Products: Ibm Maximo for Oil and Gas, Ibm Maximo Health\, Safety and Environment Manager.

## How do I fix CVE-2019-4546?

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

## Is CVE-2019-4546 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-4546 and fix it if it is affected.

What it is: CVE-2019-4546 is a medium-severity vulnerability in IBM Maximo Health- Safety and Environment Manager, published on 28 Oct 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-4546 in the wild and no public exploit code.

Affected product: IBM Maximo Health- Safety and Environment Manager. 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-2019-4546/ (Markdown: https://insights.sbomify.com/CVE-2019-4546/index.md)
```

## Sources

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

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