LiveActive security incident?Get immediate response
CVE Record

CVE-2018-6336: An issue was discovered in osquery.

An issue was discovered in osquery. 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. This issue affects osquery prior to v3.2.7

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-6336 affects osquery before v3.2.7. A specially crafted macOS Universal/fat binary could appear Apple-signed to a third-party check while unsigned malicious code actually runs. Business risk is highest where endpoint policy, allowlisting, or investigations trusted osquery's signing result.

Executive priority

Prioritize remediation if osquery influenced endpoint trust, allowlisting, or incident response decisions on macOS. The urgency is lower for organizations not using affected osquery versions or not relying on its signing checks.

Technical view

The flaw is incomplete inspection of Universal/fat binaries during third-party Apple code-signing checks. The CVE rates it CVSS 7.8: local attack vector, low complexity, no privileges required, user interaction required, with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely limited to macOS environments running osquery before v3.2.7 and relying on its code-signing assessment for Universal/fat binaries. Systems not using vulnerable osquery checks are not shown affected by the provided sources.

Exploitation context

The source bundle does not report active exploitation, and the CVE is not marked KEV. Exploitation requires a maliciously crafted local binary and user interaction, but could undermine trust decisions that treat apparent Apple signatures as safe.

Researcher notes

Evidence supports an osquery code-signing validation bypass before v3.2.7. The provided sources do not establish real-world exploitation, detailed affected platform scope beyond macOS Universal/fat binary handling, or compensating controls beyond upgrading and checking guidance.

Mitigation direction

  • Upgrade osquery to v3.2.7 or later.
  • Check current osquery vendor guidance before closing remediation.
  • Treat prior osquery signing results for Universal/fat binaries as untrusted.
  • Review allowlists or policy decisions based on vulnerable signing checks.

Validation and detection

  • Inventory osquery versions across macOS endpoints.
  • Identify workflows relying on osquery-reported Apple signing status.
  • Confirm Universal/fat binaries receive full architecture-slice inspection.
  • Review historical detections involving Apple-signed classifications before v3.2.7.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-254: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-6336 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2018-6336Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Facebookosquery3.2.7, unspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-254 · source CWE mapping

7PK - Security Features

7PK - Security Features represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.