{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-22410 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-22410 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-22410 is a low-severity vulnerability in gluwa creditcoin, published on 17 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-22410 and fix it if it is affected.\n\nWhat it is: CVE-2024-22410 is a low-severity vulnerability in gluwa creditcoin, published on 17 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-22410 in the wild and no public exploit code.\n\nAffected product: gluwa creditcoin. 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-22410/ (Markdown: https://insights.sbomify.com/CVE-2024-22410/index.md)","id":"CVE-2024-22410","markdown":"https://insights.sbomify.com/CVE-2024-22410/index.md","name":"CVE-2024-22410","record":{"aliases":[],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Creditcoin node","requires_auth":"low_privilege","summary":"Attackers with write access to the program directory can replace DLLs to execute arbitrary code on Windows Creditcoin nodes.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"creditcoin","vendor":"gluwa"}],"cvss":{"score":3.3,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-426","name":"Untrusted Search Path"}],"description":"Creditcoin is a network that enables cross-blockchain credit transactions. The Windows binary of the Creditcoin node loads a suite of DLLs provided by Microsoft at startup. If a malicious user has access to overwrite the program files directory it is possible to replace these DLLs and execute arbitrary code. It is the view of the blockchain development team that the threat posed by a hypothetical binary planting attack is minimal and represents a low-security risk. The vulnerable DLL files are from the Windows networking subsystem, the Visual C++ runtime, and low-level cryptographic primitives. Collectively these dependencies are required for a large ecosystem of applications, ranging from enterprise-level security applications to game engines, and don’t represent a fundamental lack of security or oversight in the design and implementation of Creditcoin. The blockchain team takes the stance that running Creditcoin on Windows is officially unsupported and at best should be thought of as experimental.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Binary Planting Attack on Windows Platforms in Creditcoin","id":"CVE-2024-22410","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Cross site scripting in Action messages on Avo","id":"CVE-2024-22411"},"packages":[],"prev":{"headline":"Default Privileges allow for high level operations for low privileged users in datahub","id":"CVE-2024-22409"},"products":["creditcoin"],"published":"2024-01-17","related":[],"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":"2024-11-13","vendors":["gluwa"]},"summary":"Attackers with write access to the program directory can replace DLLs to execute arbitrary code on Windows Creditcoin nodes.","url":"https://insights.sbomify.com/CVE-2024-22410/"}