Account compromise via default weak password policy
Published Jan 29, 2025 · Updated Feb 12, 2025
Weak password requirements in IBM Aspera Faspex 5.0.0 through 5.0.10 allow remote attackers to compromise user accounts. The default account policy does not require strong passwords; an administrator-controlled setting, when enabled, requires new passwords to contain a letter, number, and symbol. Exploitation requires guessing or obtaining a password accepted under the weak default policy, and resulting access is bounded by the compromised account's permissions.
Summary
What happened
Weak password requirements in IBM Aspera Faspex 5.0.0 through 5.0.10 allow remote attackers to compromise user accounts. The default account policy does not require strong passwords; an administrator-controlled setting, when enabled, requires new passwords to contain a letter, number, and symbol. Exploitation requires guessing or obtaining a password accepted under the weak default policy, and resulting access is bounded by the compromised account's permissions.
The record
- CVE
- CVE-2023-37398
- Published
- Jan 29, 2025
- Updated
- Feb 12, 2025
- Vendor
- IBM
- Product
- IBM Aspera Faspex
- Classifications
- CWE-521, T1110.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 29, 2025CVE publishedPublication date reported by the CVE source.
- Feb 12, 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=5.0.0 <=5.0.10
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