CVE-2024-41255

Filestash 0.4

Published

31 July 2024

Modified

29 September 2025

CVSS Score v3.1 7.5

Click a component to see what it means

Raw vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS Score 0.0026 17th percentile

Risk Priority 54 floored blend · peak EPSS

Summary

CVE-2024-41255 is a high-severity Insecure Default Variable Initialization (CWE-453) vulnerability in Filestash Filestash. Its CVSS base score is 7.5 (High).

Operationally, ranked at the 17th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to CM-2 (Baseline Configuration) and CM-6 (Configuration Settings) — see the control section below for these in your framework.

EU & UK References

🇪🇺 ENISA EUVD: EUVD-2024-2245

Vulnerability Data

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.

CWE(s): CWE-453

Related Threats

CVEs Like This One

CVE-2024-41256Same product: Filestash Filestash

CVE-2024-41258Same product: Filestash Filestash

CVE-2026-0082Shared CWE-453

CVE-2026-41330Shared CWE-453

CVE-2024-21411Shared CWE-453

CVE-2025-47945Shared CWE-453

CVE-2024-39916Shared CWE-453

CVE-2025-61926Shared CWE-453

CVE-2023-27516Shared CWE-453

CVE-2024-49120Shared CWE-453

Affected Assets

filestash

0.4

Mitigating Controls

Control response

Prevent

Stop it (NIST 800-53)

—

Detect

Catch it (NIST detect / respond)

—

Harden

Shrink the surface (DISA STIG)

4 hardening rules · 2 OS baselines

Validate

Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

CM-6 Configuration Settings good match

Requires establishing the most restrictive configuration settings, which directly overrides or prevents use of insecure default variable initializations.

CM-2 Baseline Configuration good match

Requires maintaining a documented baseline configuration that can enforce secure initial values instead of insecure defaults.

SA-8 Security and Privacy Engineering Principles partial match

Mandates application of security engineering principles during development that include use of secure defaults and proper variable initialization.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-01 mostly match

prevents

Hardened baselines and configuration management directly replace insecure product defaults with secure values.

PR.PS-06 mostly match

prevents

Secure software development practices explicitly include choosing safe initial values instead of insecure defaults.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match

finds

Security testing can detect insecure defaults but does not prevent them.

A.8.9 Configuration management mostly match

prevents

Configuration management enforces secure default values and prevents insecure initialization.

A.8.25 Secure development life cycle partial match

prevents

Secure development life cycle requires explicit secure initialization of variables.

A.8.27 Secure system architecture and engineering principles partial match

prevents

Secure architecture principles include avoiding insecure defaults in design.