# CVE-2024-41255: Filestash configured to skip TLS certificate verification when using the FTPS protocol

> Filestash skips TLS verification for FTPS, allowing man-in-the-middle attacks to intercept or modify data.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 31 Jul 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-4jmm-c6jw-g796, GO-2024-3033

## What is CVE-2024-41255?

CVE-2024-41255 is a high-severity vulnerability in n/a, published on 31 Jul 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

filestash v0.4 is configured to skip TLS certificate verification when using the FTPS protocol, possibly allowing attackers to execute a man-in-the-middle attack via the Init function of index.go.

Weakness: CWE-453 (Insecure Default Variable Initialization)

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

3 open source packages ship an affected version, including github.com/mickael-kerjean/filestash. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/mickael-kerjean/filestash` | Go | All versions | None |
| `github.com/mickael-kerjean/filestash` | Go | All versions to 0.4 | None |
| `github.com/mickael-kerjean/filestash` | Go | All versions to 0.4 | None |

Products: Filestash Filestash.

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

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

## Is CVE-2024-41255 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-41256](https://insights.sbomify.com/CVE-2024-41256/): Filestash skips TLS certificate verification process when sending out email verification codes (medium 5.9)
- [CVE-2024-41258](https://insights.sbomify.com/CVE-2024-41258/): An issue was discovered in filestash v0.4. (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-41255 is a high-severity vulnerability in n/a, published on 31 Jul 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-41255 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/mickael-kerjean/filestash (Go): affected all versions; no fix listed
- github.com/mickael-kerjean/filestash (Go): affected all versions up to 0.4; no fix listed
- github.com/mickael-kerjean/filestash (Go): affected all versions up to 0.4; no fix listed

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-41255/ (Markdown: https://insights.sbomify.com/CVE-2024-41255/index.md)
```

## Sources

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

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