# CVE-2024-41256: Filestash skips TLS certificate verification process when sending out email verification codes

> Attackers can intercept email verification codes via man-in-the-middle attacks due to disabled TLS certificate verification in default configurations.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Jul 2024
- **Updated:** 18 Mar 2025
- **Also known as:** GHSA-mpvx-whpp-99xj, GO-2024-3035

## What is CVE-2024-41256?

CVE-2024-41256 is a medium-severity vulnerability in n/a, published on 31 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Default configurations in the ShareProofVerifier function of filestash v0.4 causes the application to skip the TLS certificate verification process when sending out email verification codes, possibly allowing attackers to access sensitive data via a man-in-the-middle attack.

Weakness: CWE-295 (Improper Certificate Validation)

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

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-41256?

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

## Is CVE-2024-41256 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-41255](https://insights.sbomify.com/CVE-2024-41255/): Filestash configured to skip TLS certificate verification when using the FTPS protocol (high 7.5)
- [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-41256 and fix it if it is affected.

What it is: CVE-2024-41256 is a medium-severity vulnerability in n/a, published on 31 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-41256 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-41256/ (Markdown: https://insights.sbomify.com/CVE-2024-41256/index.md)
```

## Sources

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

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