{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-41258 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-41258 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-41258 is a medium-severity vulnerability in n/a, published on 31 Jul 2024."},"fix_prompt":"Check this codebase for CVE-2024-41258 and fix it if it is affected.\n\nWhat it is: CVE-2024-41258 is a medium-severity vulnerability in n/a, published on 31 Jul 2024. \nExploitation: There is no known exploitation of CVE-2024-41258 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-41258/ (Markdown: https://insights.sbomify.com/CVE-2024-41258/index.md)","id":"CVE-2024-41258","markdown":"https://insights.sbomify.com/CVE-2024-41258/index.md","name":"CVE-2024-41258","record":{"aliases":["GHSA-f6rc-73vx-29h5"],"analysis":null,"analysis_generated_by":null,"assigner":"mitre","cpe":[{"product":"filestash","vendor":"filestash"}],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"},{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"An issue was discovered in filestash v0.4. The usage of the ssh.InsecureIgnoreHostKey() disables host key verification, possibly allowing attackers to obtain sensitive information via a man-in-the-middle attack.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"An issue was discovered in filestash v0.4.","id":"CVE-2024-41258","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Navidrome uses MD5 hashing algorithm","id":"CVE-2024-41259"},"packages":[],"prev":{"headline":"Filestash skips TLS certificate verification process when sending out email verification codes","id":"CVE-2024-41256"},"products":["n/a"],"published":"2024-07-31","related":[{"cvss_score":7.5,"headline":"Filestash configured to skip TLS certificate verification when using the FTPS protocol","id":"CVE-2024-41255","kev_date_added":null,"published":"2024-07-31"},{"cvss_score":5.9,"headline":"Filestash skips TLS certificate verification process when sending out email verification codes","id":"CVE-2024-41256","kev_date_added":null,"published":"2024-07-31"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-13","vendors":["n/a"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2024-41258/"}