# CVE-2024-5275: Hardcoded credentials in FileCatalyst Direct

> Hard-coded password allows keystore access, enabling private key extraction and potential man-in-the-middle attacks against FileCatalyst users.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jun 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-6mp6-w28p-c8jp

## What is CVE-2024-5275?

CVE-2024-5275 is a high-severity vulnerability in Fortra FileCatalyst Direct, published on 18 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-259 (Use of Hard-coded Password)

## Which versions are affected by CVE-2024-5275?


## How do I fix CVE-2024-5275?

No fix has been published for CVE-2024-5275 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-5275 being exploited?

There is no known exploitation of CVE-2024-5275 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-5275 and fix it if it is affected.

What it is: CVE-2024-5275 is a high-severity vulnerability in Fortra FileCatalyst Direct, published on 18 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-5275 in the wild and no public exploit code.

Affected product: Fortra FileCatalyst Direct. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-5275/ (Markdown: https://insights.sbomify.com/CVE-2024-5275/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-5275
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-5275
- OSV: https://osv.dev/vulnerability/CVE-2024-5275

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-5275/
Summaries are generated and may contain mistakes; the official description above is the record.