Credential stuffing via unprotected credential transport
Published Jul 30, 2024 · Updated Aug 12, 2024
Unprotected credential transport in OpenText Documentum Server 16.7 through 23.4 allows local users to expose credentials for stuffing attacks. OpenText identifies the flaw as unprotected credential transport but has not published the affected protocol, code path, or operation that leaves credentials exposed. Exploitation requires high privileges and additional local attack conditions; successful credential reuse compromises repository access and data.
Summary
What happened
Unprotected credential transport in OpenText Documentum Server 16.7 through 23.4 allows local users to expose credentials for stuffing attacks. OpenText identifies the flaw as unprotected credential transport but has not published the affected protocol, code path, or operation that leaves credentials exposed. Exploitation requires high privileges and additional local attack conditions; successful credential reuse compromises repository access and data.
The record
- CVE
- CVE-2024-4188
- Published
- Jul 30, 2024
- Updated
- Aug 12, 2024
- Vendor
- OpenText
- Product
- Documentum Server
- Classifications
- CWE-523, CAPEC-600, T1110.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jul 30, 2024CVE publishedPublication date reported by the CVE source.
- Aug 12, 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=16.7 <=23.4
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