Account compromise via weak default password policy
Published Apr 7, 2023 · Updated Feb 10, 2025
Weak password requirements in IBM Sterling Order Management 10.0 allow remote attackers to compromise user accounts by guessing passwords. The default password-policy configuration does not enforce strong passwords, and IBM has not published a lower-level implementation locus for that default. Network access to an authentication interface and a guessable account password are required, and successful access remains bounded by the compromised account's permissions.
Summary
What happened
Weak password requirements in IBM Sterling Order Management 10.0 allow remote attackers to compromise user accounts by guessing passwords. The default password-policy configuration does not enforce strong passwords, and IBM has not published a lower-level implementation locus for that default. Network access to an authentication interface and a guessable account password are required, and successful access remains bounded by the compromised account's permissions.
The record
- CVE
- CVE-2022-34333
- Published
- Apr 7, 2023
- Updated
- Feb 10, 2025
- Vendor
- IBM
- Product
- IBM Sterling Order Management
- Classifications
- CWE-521, T1110.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 7, 2023CVE publishedPublication date reported by the CVE source.
- Feb 10, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo