Hard-coded password in FileCatalyst Direct 3.8.10 Build 138 TransferAgent (and earlier) and FileCatalyst Workflow 5.1.6 Build 130 (and earlier)
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Fortra | FileCatalyst Direct | unaffected |
|
||||||
| Fortra | FileCatalyst Workflow | unaffected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Fortra | Filecatalyst Direct | — |
| Fortra | Filecatalyst Workflow | — |
Vendor Solution
For FileCatalyst Direct users, upgrade to 3.8.10 build 144 (or higher) For FileCatalyst Workflow users, upgrade to 5.1.6 build 133 (or later) For those using the FileCatalyst TransferAgent remotely, e.g., as a remote-controlled node accepting REST calls, update REST calls to "http". If "https" is still required, a new SSL key and add it to the agent keystore.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2024-46511 | A hard-coded password in the FileCatalyst TransferAgent can be found which can be used to unlock the keystore from which contents may be read out, for example, the private key for certificates. Exploit of this vulnerability could lead to a machine-in-the-middle (MiTM) attack against users of the agent. This issue affects all versions of FileCatalyst Direct from 3.8.10 Build 138 and earlier and all versions of FileCatalyst Workflow from 5.1.6 Build 130 and earlier. |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.114% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.
Use of Hard-coded Password