# CVE-2022-34333: IBM Sterling Order Management information disclosure

> Weak default password requirements in IBM Sterling Order Management allow attackers to compromise user accounts.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Apr 2023
- **Updated:** 10 Feb 2025
- **Also known as:** GHSA-8x8m-w3j5-xj5p

## What is CVE-2022-34333?

CVE-2022-34333 is a medium-severity vulnerability in IBM Sterling Order Management, published on 7 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IBM Sterling Order Management 10.0 does not require that users should have strong passwords by default, which makes it easier for attackers to compromise user accounts. IBM X-Force ID: 229698.

Weakness: CWE-521 (Weak Password Requirements)

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

It affects 1 product.


Products: Ibm Sterling Order Management.

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

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

## Is CVE-2022-34333 being exploited?

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

## Other vulnerabilities in IBM Sterling Order Management

- [CVE-2021-20554](https://insights.sbomify.com/CVE-2021-20554/): Cross-site scripting in Sterling Order Management (medium 6.1)
- [CVE-2022-33959](https://insights.sbomify.com/CVE-2022-33959/): IBM Sterling Order Management privilege escalation (medium 5.4)
- [CVE-2014-0932](https://insights.sbomify.com/CVE-2014-0932/): Cross-site scripting in n/a (low 3.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-34333 is a medium-severity vulnerability in IBM Sterling Order Management, published on 7 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-34333 in the wild and no public exploit code.

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

## Sources

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

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