Security readout for executives and security teams
CVE-2020-27930 is an Apple font-processing memory corruption flaw. A maliciously crafted font could cause arbitrary code execution on affected macOS, iOS, iPadOS, and watchOS devices. Apple fixed it in multiple 2020 updates. CISA lists it in KEV, so treat unpatched devices as a real-world exposure, not a theoretical issue. Exposure is most likely on Apple devices that have not installed the listed 2020 security updates or later supported releases. The affected version data is not granular in the bundle, so validation should rely on actual OS build and Apple advisory coverage rather than product name alone. High priority for patch assurance. The business issue is arbitrary code execution on Apple endpoints plus CISA KEV known-exploitation status. Focus on proving fleet update coverage, especially older macOS and iOS devices that may have missed 2020 security updates. Mitigation focus: Install the relevant Apple security update or a later supported OS release.; Prioritize Macs, iPhones, iPads, and watches below the fixed versions listed by Apple.; Remove or isolate devices that cannot receive supported Apple updates..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-787: 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2020-27930 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- Yes
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
CISA KEV status
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H1.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://support.apple.com/en-us/HT211931CVE reference · x_refsource_MISC
- https://support.apple.com/en-us/HT211928CVE reference · x_refsource_MISC
- https://support.apple.com/en-us/HT211929CVE reference · x_refsource_MISC
- https://support.apple.com/en-us/HT211940CVE reference · x_refsource_MISC
- https://support.apple.com/en-us/HT211944CVE reference · x_refsource_MISC
- https://support.apple.com/en-us/HT211945CVE reference · x_refsource_MISC
- https://support.apple.com/en-us/HT211946CVE reference · x_refsource_MISC
- https://support.apple.com/en-us/HT211947CVE reference · x_refsource_MISC
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2020-27930CVE reference · government-resource
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.