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

Q: How do I fix CVE-2018-10404?

knockknock: upgrade to newer than 1.9.3; lulu: upgrade to newer than 0.9.8; procinfo: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Q: Is CVE-2018-10404 being exploited?

CVE-2018-10404 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2018-10404 affect?

CVE-2018-10404 affects knockknock, lulu, procinfo. Severity is high (CVSS 7.8). 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/f

Q: How urgent is CVE-2018-10404?

Priority 47/100. High severity; Public exploit reference

This month

HIGH 7.8UPGRADEUPGRADEMITIGATE

CVE-2018-10404 is a high-severity flaw (CVSS 7.8) affecting knockknock, lulu, procinfo. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	7.8 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.8% (top 42%)
CISA exploited list	No
Weakness	CWE-295
Published	2018-06-13
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: objective-see

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-06-13 22:29 UTCPublished CVE record published
2026-06-17 01:33 UTCUpdated Record last modified

objective-see knockknock UPGRADE

Affected: <= 1.9.3

Fixed in: newer than 1.9.3

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy knockknock || rpm -q knockknock || knockknock --version

2. UPGRADE to newer than 1.9.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade knockknock

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade knockknock

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

objective-see lulu UPGRADE

Affected: <= 0.9.8

Fixed in: newer than 0.9.8

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy lulu || rpm -q lulu || lulu --version

2. UPGRADE to newer than 0.9.8 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade lulu

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade lulu

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

objective-see procinfo MITIGATE

Affected: all versions

Fixed in: no fixed release known

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy procinfo || rpm -q procinfo || procinfo --version

No fixed or unaffected release known

Apply the vendor mitigation from the advisory, disable the affected feature, or restrict network access.

objective-see taskexplorer UPGRADE

Affected: <= 1.6.0

Fixed in: newer than 1.6.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy taskexplorer || rpm -q taskexplorer || taskexplorer --version

2. UPGRADE to newer than 1.6.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade taskexplorer

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade taskexplorer

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

objective-see whatsyoursign UPGRADE

Affected: <= 1.4.0

Fixed in: newer than 1.4.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy whatsyoursign || rpm -q whatsyoursign || whatsyoursign --version

2. UPGRADE to newer than 1.4.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade whatsyoursign

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade whatsyoursign

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2018-10404?

knockknock: upgrade to newer than 1.9.3; lulu: upgrade to newer than 0.9.8; procinfo: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2018-10404 being exploited?

CVE-2018-10404 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2018-10404 affect?

CVE-2018-10404 affects knockknock, lulu, procinfo. Severity is high (CVSS 7.8). 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/f

How urgent is CVE-2018-10404?

Priority 47/100. High severity; Public exploit reference

References

← Back to latest CVEs