What is the severity of CVE-2018-10408?

CVE-2018-10408 is classified as a moderate severity vulnerability due to its potential to allow execution of malicious code.

How does CVE-2018-10408 exploit third-party code signing checks?

CVE-2018-10408 exploits third-party code signing checks by allowing an unsigned Universal/fat binary to be misidentified as a legitimate Apple-signed binary.

What types of software are affected by CVE-2018-10408?

CVE-2018-10408 specifically affects the VirusTotal tool that analyzes code for potential threats.

How can users mitigate the risks associated with CVE-2018-10408?

Users can mitigate risks related to CVE-2018-10408 by ensuring that they only use trusted sources for binaries and keeping their VirusTotal software updated.

What actions should be taken if a malicious binary is detected due to CVE-2018-10408?

If a malicious binary is detected due to CVE-2018-10408, users should immediately remove the binary and scan their systems for further compromises.

Vulnerability/
CVE-2018-10408

high

7.8

CWE

295

13/6/2018

5/8/2024

CVE-2018-10408

First published: Wed Jun 13 2018(Updated: )

An issue was discovered in VirusTotal. 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.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Virustotal Virustotal

Never miss a vulnerability like this again

Reference Links

https://www.okta.com/security-blog/2018/06/issues-around-third-party-apple-code-signing-checks/

Frequently Asked Questions

What is the severity of CVE-2018-10408?
CVE-2018-10408 is classified as a moderate severity vulnerability due to its potential to allow execution of malicious code.
How does CVE-2018-10408 exploit third-party code signing checks?
CVE-2018-10408 exploits third-party code signing checks by allowing an unsigned Universal/fat binary to be misidentified as a legitimate Apple-signed binary.
What types of software are affected by CVE-2018-10408?
CVE-2018-10408 specifically affects the VirusTotal tool that analyzes code for potential threats.
How can users mitigate the risks associated with CVE-2018-10408?
Users can mitigate risks related to CVE-2018-10408 by ensuring that they only use trusted sources for binaries and keeping their VirusTotal software updated.
What actions should be taken if a malicious binary is detected due to CVE-2018-10408?
If a malicious binary is detected due to CVE-2018-10408, users should immediately remove the binary and scan their systems for further compromises.

collector/nvd-index
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/author
agent/weakness
agent/tags
agent/last-modified-date
agent/references
agent/description
agent/first-publish-date
agent/event
agent/source
vendor/virustotal
canonical/virustotal virustotal

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2018-10408?
CVE-2018-10408 is classified as a moderate severity vulnerability due to its potential to allow execution of malicious code.
How does CVE-2018-10408 exploit third-party code signing checks?
CVE-2018-10408 exploits third-party code signing checks by allowing an unsigned Universal/fat binary to be misidentified as a legitimate Apple-signed binary.
What types of software are affected by CVE-2018-10408?
CVE-2018-10408 specifically affects the VirusTotal tool that analyzes code for potential threats.
How can users mitigate the risks associated with CVE-2018-10408?
Users can mitigate risks related to CVE-2018-10408 by ensuring that they only use trusted sources for binaries and keeping their VirusTotal software updated.
What actions should be taken if a malicious binary is detected due to CVE-2018-10408?
If a malicious binary is detected due to CVE-2018-10408, users should immediately remove the binary and scan their systems for further compromises.