CVE-2024-41256 json
Filestash skips TLS certificate verification process when sending out email verification codes
published 2024-07-31 2 y ago modified 2026-09-10 1 mo ago also GHSA-mpvx-whpp-99xj , GO-2024-3035 , EUVD-2024-2386
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 10%
- public exploits
- 0
- none known
Summary
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.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/mickael-kerjean/filestash | <=0.4 all versions |
no fix listed |
Classification
- Weakness
-
- CWE-295 Improper Certificate Validation
References
-
gist.github.com
/nyxfqq/a6da3fe6128b978ea1aaa5df639d5f98
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2024-41256
advisory
-
github.com
/mickael-kerjean/filestash/issues/709
web, report
-
github.com
/mickael-kerjean/filestash
package
-
github.com
/mickael-kerjean/filestash/blob/master/server/model/share.go#L132
web
-
pkg.go.dev
/vuln/GO-2024-3035
web
-
github.com
/advisories/GHSA-mpvx-whpp-99xj
advisory
Sources
- CVE List CVE-2024-41256
- GitHub Advisory GHSA-mpvx-whpp-99xj
- NVD CVE-2024-41256
- OSV GO-2024-3035
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.