# CVE-2022-46774: IBM Manage Application security bypass

> Incorrect default permissions in IBM Manage Application allow unauthorized users to perform restricted actions, requiring a patch to enforce proper access controls.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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:** 15 Mar 2023
- **Updated:** 26 Feb 2025
- **Also known as:** GHSA-6qfq-9m7h-9wwm

## What is CVE-2022-46774?

CVE-2022-46774 is a medium-severity missing authorization vulnerability in IBM Manage Application, published on 15 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM Manage Application 8.8.0 and 8.9.0 in the IBM Maximo Application Suite is vulnerable to incorrect default permissions which could give access to a user to actions that they should not have access to.  IBM X-Force ID:  242953.

Weakness: CWE-276 (Incorrect Default Permissions), CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2022-46774?

It affects 1 product.


Products: Ibm Manage Application.

## How do I fix CVE-2022-46774?

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

## Is CVE-2022-46774 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-46774 and fix it if it is affected.

What it is: CVE-2022-46774 is a medium-severity missing authorization vulnerability in IBM Manage Application, published on 15 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-46774 in the wild and no public exploit code.

Affected product: IBM Manage Application. 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-2022-46774/ (Markdown: https://insights.sbomify.com/CVE-2022-46774/index.md)
```

## Sources

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

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