Private-key disclosure via hard-coded keystore password
Published Jun 18, 2024 · Updated Aug 1, 2024
A hard-coded TransferAgent password allows local users to extract private keys from affected FileCatalyst Direct and Workflow builds. TransferAgent embeds the password protecting its keystore, allowing local users to unlock the store and read certificate private keys. Local low-privileged access is required; Direct 3.8.10 Build 138 and earlier and Workflow 5.1.6 Build 130 and earlier are affected, and stolen keys enable man-in-the-middle impersonation.
Summary
What happened
A hard-coded TransferAgent password allows local users to extract private keys from affected FileCatalyst Direct and Workflow builds. TransferAgent embeds the password protecting its keystore, allowing local users to unlock the store and read certificate private keys. Local low-privileged access is required; Direct 3.8.10 Build 138 and earlier and Workflow 5.1.6 Build 130 and earlier are affected, and stolen keys enable man-in-the-middle impersonation.
The record
- CVE
- CVE-2024-5275
- Published
- Jun 18, 2024
- Updated
- Aug 1, 2024
- Vendor
- Fortra
- Product
- FileCatalyst Direct
- Classifications
- CWE-259, T1552.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 18, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 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=3.7 <3.8.10
- Affected versionversion=3.7 <=3.8.10.138
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