{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-10470 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-10470 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-10470 is a medium-severity vulnerability in Objective Development Software GmbH Little Snitch, published on 12 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-10470 and fix it if it is affected.\n\nWhat it is: CVE-2018-10470 is a medium-severity vulnerability in Objective Development Software GmbH Little Snitch, published on 12 Jun 2018. 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-2018-10470 in the wild and no public exploit code.\n\nAffected product: Objective Development Software GmbH Little Snitch. 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-2018-10470/ (Markdown: https://insights.sbomify.com/CVE-2018-10470/index.md)","id":"CVE-2018-10470","markdown":"https://insights.sbomify.com/CVE-2018-10470/index.md","name":"CVE-2018-10470","record":{"aliases":["GHSA-j3vp-xqjf-c8pj"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"macOS firewall application","requires_auth":"none","summary":"Attackers can bypass Little Snitch's code signature validation by crafting multi-architecture binaries, confusing users about the validity of running processes.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"obdev","cpe":[{"product":"little_snitch","vendor":"objective_development"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"Little Snitch versions 4.0 to 4.0.6 use the SecStaticCodeCheckValidityWithErrors() function without the kSecCSCheckAllArchitectures flag and therefore do not validate all architectures stored in a fat binary. An attacker can maliciously craft a fat binary containing multiple architectures that may cause a situation where Little Snitch treats the running process as having no code signature at all while erroneously indicating that the binary on disk does have a valid code signature. This could lead to users being confused about whether or not the code signature is valid.","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":"Security feature bypass in Little Snitch","id":"CVE-2018-10470","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2018-10471"},"packages":[],"prev":{"headline":"File upload in n/a","id":"CVE-2018-10469"},"products":["Little Snitch"],"published":"2018-06-12","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["Objective Development Software GmbH"]},"summary":"Attackers can bypass Little Snitch's code signature validation by crafting multi-architecture binaries, confusing users about the validity of running processes.","url":"https://insights.sbomify.com/CVE-2018-10470/"}