{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-41880 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-41880 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-41880 is a medium-severity vulnerability in n/a, published on 22 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-41880 and fix it if it is affected.\n\nWhat it is: CVE-2024-41880 is a medium-severity vulnerability in n/a, published on 22 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-41880 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-41880/ (Markdown: https://insights.sbomify.com/CVE-2024-41880/index.md)","id":"CVE-2024-41880","markdown":"https://insights.sbomify.com/CVE-2024-41880/index.md","name":"CVE-2024-41880","record":{"aliases":["GHSA-679x-v483-q6x9"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Veilid core library","requires_auth":"none","summary":"Attackers can misuse the ping function to reduce the effectiveness of safety and private routes in the Veilid protocol.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-203","name":"Observable Discrepancy"}],"description":"In veilid-core in Veilid before 0.3.4, the protocol's ping function can be misused in a way that decreases the effectiveness of safety and private routes.","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":"Security feature bypass in n/a","id":"CVE-2024-41880","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in SDoP","id":"CVE-2024-41881"},"packages":[],"prev":{"headline":"RE: New Edge T5 MSRC Case [DCMSFT-1294]","id":"CVE-2024-41879"},"products":["n/a"],"published":"2024-07-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["n/a"]},"summary":"Attackers can misuse the ping function to reduce the effectiveness of safety and private routes in the Veilid protocol.","url":"https://insights.sbomify.com/CVE-2024-41880/"}