# CVE-2018-10404: An issue was discovered in Objective-See KnockKnock, LuLu, TaskExplorer, WhatsYourSign, and procInfo.


- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mgx8-qf37-pr57

## What is CVE-2018-10404?

CVE-2018-10404 is a high-severity vulnerability in n/a, published on 13 Jun 2018. 

### Official 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.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2018-10404?

It affects 5 products.


Products: Objective-See Knockknock, Objective-See Lulu, Objective-See Procinfo, Objective-See Taskexplorer, Objective-See Whatsyoursign.

## How do I fix CVE-2018-10404?

No fix has been published for CVE-2018-10404 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-10404 being exploited?

There is no known exploitation of CVE-2018-10404 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-10404 and fix it if it is affected.

What it is: CVE-2018-10404 is a high-severity vulnerability in n/a, published on 13 Jun 2018. 
Exploitation: There is no known exploitation of CVE-2018-10404 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-10404/ (Markdown: https://insights.sbomify.com/CVE-2018-10404/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-10404
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-10404
- OSV: https://osv.dev/vulnerability/CVE-2018-10404

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-10404/
Summaries are generated and may contain mistakes; the official description above is the record.