Account compromise via one-character password acceptance
Published May 22, 2023 · Updated Oct 11, 2024
Weak password requirements in Apache InLong 1.1.0 through 1.6.0 allow remote attackers to access accounts by guessing simple passwords. UserRequest validates both password and newPassword at only one to 64 characters, so a one-character password passes the manager input constraint. Exploitation requires an account whose user selected such a short password; successful guessing grants only that account's assigned privileges.
Summary
What happened
Weak password requirements in Apache InLong 1.1.0 through 1.6.0 allow remote attackers to access accounts by guessing simple passwords. UserRequest validates both password and newPassword at only one to 64 characters, so a one-character password passes the manager input constraint. Exploitation requires an account whose user selected such a short password; successful guessing grants only that account's assigned privileges.
The record
- CVE
- CVE-2023-31098
- Published
- May 22, 2023
- Updated
- Oct 11, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache InLong
- Classifications
- CWE-521, CAPEC-16, CAPEC-49, T1110.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 22, 2023CVE publishedPublication date reported by the CVE source.
- Oct 11, 2024Record 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=1.1.0 <=1.6.0
What conditions does exploitation require?
What is affected?
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