{"answers":{"affected":"It affects 5 products.","exploited":"There is no known exploitation of CVE-2018-10404 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-10404 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-10404 is a high-severity vulnerability in n/a, published on 13 Jun 2018."},"fix_prompt":"Check this codebase for CVE-2018-10404 and fix it if it is affected.\n\nWhat it is: CVE-2018-10404 is a high-severity vulnerability in n/a, published on 13 Jun 2018. \nExploitation: There is no known exploitation of CVE-2018-10404 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-2018-10404/ (Markdown: https://insights.sbomify.com/CVE-2018-10404/index.md)","id":"CVE-2018-10404","markdown":"https://insights.sbomify.com/CVE-2018-10404/index.md","name":"CVE-2018-10404","record":{"aliases":["GHSA-mgx8-qf37-pr57"],"analysis":null,"analysis_generated_by":null,"assigner":"mitre","cpe":[{"product":"knockknock","vendor":"objective-see"},{"product":"lulu","vendor":"objective-see"},{"product":"procinfo","vendor":"objective-see"},{"product":"taskexplorer","vendor":"objective-see"},{"product":"whatsyoursign","vendor":"objective-see"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"An issue was discovered in Objective-See KnockKnock, LuLu, TaskExplorer, WhatsYourSign, and procInfo. A maliciously crafted Universal/fat binary can evade third-party code signing checks. By not completing full inspection of the Universal/fat binary, the user of the third-party tool will believe that the code is signed by Apple, but the malicious unsigned code will execute.","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 Objective-See KnockKnock, LuLu, TaskExplorer, WhatsYourSign, and procInfo.","id":"CVE-2018-10404","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2018-10405"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2018-10403"},"products":["n/a"],"published":"2018-06-13","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-08-05","vendors":["n/a"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2018-10404/"}