CVE-2017-2410: It allows attackers to execute arbitrary code in a privileged context via a crafted app

Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Fix not verified

What, why and how

An issue was discovered in certain Apple products. macOS before 10.12.4 is affected. The issue involves the "Kernel" component. It allows attackers to execute arbitrary code in a privileged context via a crafted app.

What

Why

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How

An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may execute code or commands in the affected security context.

What

Why

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path: local access → Improper Input Validation → execute code or commands in the affected security context
Attack surface: Local
Privileges required: None: unauthenticated exploitation is possible
User interaction: Required interaction required
Attack complexity: Low: no specialised conditions are recorded
Security boundary: Unchanged: impact remains within the vulnerable component's security authority
Weakness ? CWE means Common Weakness Enumeration: a standard category for the underlying weakness.: CWE-20 ↗
CWE-20: Improper Input Validation. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
CVSS vector ? CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.: CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Common Vulnerability Scoring System 3.0: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land: After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.

UnauthenticatedRemote code executionCWE-20

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2017-11593Official EUVD mapping

0 linked advisory records.

Official EUVD record ↗

Canadian Centre for Cyber Security · English · AV17-039Multiple Apple security updates

-2016-9643, CVE-2016-9935, CVE-2016-10009, CVE-2016-10010, CVE-2016-10011, CVE-2016-10012, CVE-2016-10158, CVE-2016-10159, CVE-2016-10160, CVE-2016-10161, CVE-2017-2364, CVE-2017-2367, CVE-2017-2376, CVE-2017-2377, CVE-2017-2378, CVE-2017-2379, CVE-2017-2380, CVE-2017-2381, CVE-2017-2382, CVE-2017-2384, CVE-2017-2385, CVE-2017-2386, CVE-2017-2389, CVE-2017-2390, CVE-2017-2391, CVE-2017-2392, CVE-2017-2393, CVE-2017-2394, CVE-2017-2395, CVE-2017-2396, CVE-2017-2397, CVE-2017-2398, CVE-2017-2399, CVE-2017-2400, CVE-2017-2401, CVE-2017-2402, CVE-2017-2403, CVE-2017-2404, CVE-2017-2405, CVE-2017-2406, CVE-2017-2407, CVE-2017-2408, CVE-2017-2409, CVE-2017-2410, CVE-2017-2412, CVE-2017-2413, CVE-2017-2414, CVE-2017-2415, CVE-2017-2416, CVE-2017-2417, CVE-2017-2418, CVE-2017-2419, CVE-2017-2420, CVE-2017-2421, CVE-2017-2422, CVE-2017-2423, CVE-2017-2424, CVE-2017-2425, CVE-2017-2426, CVE-2017-2427, CVE-2017-2428, CVE-2017-2429, CVE-2017-2430, CVE-2017-2431, CVE-2017-2432, CVE-2017-2433, CVE-2017-2434, CVE-2017-2435, CVE-2017-2436, CVE-2017-2437, CVE-2017-2438, CVE-2017-2439, CVE-2017-2440, CVE-2017-2441, CVE-2017-2442, CVE-2017-2443, CVE-2017-2444, CVE-2017-2445, CVE-2017-2446, CVE-2017-2447, CVE-2017-2448, CVE-2017-2449, CVE-2017-2450, CVE-2017-2451, CVE-2017-2452, CVE-2017-2453, CVE-2017-2454, CVE

Official advisory ↗

CERT-FR · French · CERTFR-2017-AVI-092Multiples vulnérabilités dans les produits Apple

.cve.org/CVERecord?id=CVE-2017-2401 Référence CVE CVE-2017-2402 https://www.cve.org/CVERecord?id=CVE-2017-2402 Référence CVE CVE-2017-2403 https://www.cve.org/CVERecord?id=CVE-2017-2403 Référence CVE CVE-2017-2404 https://www.cve.org/CVERecord?id=CVE-2017-2404 Référence CVE CVE-2017-2405 https://www.cve.org/CVERecord?id=CVE-2017-2405 Référence CVE CVE-2017-2406 https://www.cve.org/CVERecord?id=CVE-2017-2406 Référence CVE CVE-2017-2407 https://www.cve.org/CVERecord?id=CVE-2017-2407 Référence CVE CVE-2017-2408 https://www.cve.org/CVERecord?id=CVE-2017-2408 Référence CVE CVE-2017-2409 https://www.cve.org/CVERecord?id=CVE-2017-2409 Référence CVE CVE-2017-2410 https://www.cve.org/CVERecord?id=CVE-2017-2410 Référence CVE CVE-2017-2412 https://www.cve.org/CVERecord?id=CVE-2017-2412 Référence CVE CVE-2017-2413 https://www.cve.org/CVERecord?id=CVE-2017-2413 Référence CVE CVE-2017-2414 https://www.cve.org/CVERecord?id=CVE-2017-2414 Référence CVE CVE-2017-2415 https://www.cve.org/CVERecord?id=CVE-2017-2415 Référence CVE CVE-2017-2416 https://www.cve.org/CVERecord?id=CVE-2017-2416 Référence CVE CVE-2017-2417 https://www.cve.org/CVERecord?id=CVE-2017-2417 Référence CVE CVE-2017-2418 https://www.cve.org/CVERecord?id=CVE-2017-2418 Référence CVE CVE-2017-2419 https://www.cve.org/CVERecord?id=CVE-2017-2419 Ré

Official advisory ↗

JVN iPedia · Japanese · JVNDB-2017-002390Apple macOS のカーネルコンポーネントにおける特権付きコンテキスト内で任意のコードを実行される脆弱性

Apple macOS のカーネルコンポーネントには、特権付きコンテキスト内で任意のコードを実行される脆弱性が存在します。

Official advisory ↗

Patch and workaround

Operational remediation based on structured source evidence.

Status ? Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.: Fix not verified
Affected: n/a: n/a
Fixed: No fixed version is explicitly recorded in the structured CVE data.
Action: No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
Workaround: No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.

Evidence and provenance

Published 2 Apr 2017 · Last source change 5 Aug 2024, 13:55 UTC · CWE-20 · Improper Input Validation

CVE recordCVE.org · 5.1

CVSS sourceNIST NVD

EPSS source

The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.

FIRST · tracked since 2026-09-01

European sourceENISA EUVD · EUVD-2017-11593

Product sourceCNA

Remediation sourceCVE/CNA references

CWE sourceNIST NVD

NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

5 Aug 2024, 13:55 UTC
Vendor guidanceAuthoritative vendor guidance changed from no authoritative guidance recorded to vendor advisory.
Before
no authoritative guidance recorded
After
vendor advisory
af854a3a-2127-422b-91ae-364da2661108 ↗
5 Aug 2024, 13:55 UTC
SeveritySeverity changed from Unknown to High.
Before
Unknown
After
High
NIST NVD ↗
5 Aug 2024, 13:55 UTC
CVSS scoreCVSS score changed from not recorded to 7.8 (CVSS 3.0 · NIST NVD · CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H).
Before
not recorded
After
7.8 (CVSS 3.0 · NIST NVD · CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H)
NIST NVD ↗
1 Sept 2026, 02:42 UTC
ENISA EUVD mappingEUVD-2017-11593 was added to the official ENISA EUVD mapping for this CVE.
Before
not recorded
After
{"euvdId":"EUVD-2017-11593"}
ENISA EUVD ↗
5 Aug 2024, 13:55 UTC
Catalogue recordCVE added to the BlackTree catalogue.
CNA ↗

2017-04-02CVE published

ENISA EUVD · EUVD-2017-11593↗Vendor advisory↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗

Technical terms and abbreviations used in this report

CVE: Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS: Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS: Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE: Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA: CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP: Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD: National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT: A computer security incident response team that publishes warnings or coordinates incident response.
PoC: Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF: Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL: Living off the land: abuse of legitimate tools or system functions during an attack.

It allows attackers to execute arbitrary code in a privileged context via a crafted app

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

ENISA European Vulnerability Database

EUVD-2017-11593

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

What changed after publication

It allows attackers to execute arbitrary code in a privileged context via a crafted app

National CERT insights ?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

EUVD-2017-11593

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.