CVE-2020-27950
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA memory initialization issue was addressed. This issue is fixed in macOS Big Sur 11.0.1, watchOS 7.1, iOS 12.4.9, watchOS 6.2.9, Security Update 2020-006 High Sierra, Security Update 2020-006 Mojave, iOS 14.2 and iPadOS 14.2, watchOS 5.3.9, macOS Catalina 10.15.7 Supplemental Update, macOS Catalina 10.15.7 Update. A malicious application may be able to disclose kernel memory.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a kernel memory initialization vulnerability in multiple Apple operating systems (macOS, iOS, watchOS). The issue allows a malicious local application to read kernel memory due to improper memory initialization, potentially exposing sensitive kernel data structures.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 14.2< 12.4.9>= 14.0, < 14.2< 10.15.7>= 11.0, < 11.0.1< 5.3.9>= 6.0, < 6.2.9>= 7.0, < 7.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check iOS version on iPhone or iPadGo to Settings > General > About > Version, or use the command: idevicesyslog 2>/dev/null | grep -i 'os version' or check via Apple Configurator or Finder when device is connectedAffected if Version is below 12.4.9, or between 14.0 and 14.2 (excluding 14.2)
-
Check iPadOS version on iPadGo to Settings > General > About > Version, or connect to Finder/Apple Configurator to retrieve the versionAffected if Version is below 14.2 (any version < 14.2)
-
Check macOS versionRun 'sw_vers' in Terminal, or go to Apple menu > About This Mac > VersionAffected if Version is below 10.15.7, or between 11.0 and 11.0.1 (specifically 11.0 or 11.0.1)
-
Check watchOS version on Apple WatchOpen the Watch app on paired iPhone, go to My Watch > General > About, or on the watch go to Settings > General > AboutAffected if Version is below 5.3.9, or between 6.0 and 6.2.9 (excluding 6.2.9), or between 7.0 and 7.1 (excluding 7.1)
You are affected if your device runs any of the affected OS versions listed: iOS < 12.4.9 or 14.0 <= iOS < 14.2, iPadOS < 14.2, macOS < 10.15.7 or 11.0 <= macOS < 11.0.1, or watchOS < 5.3.9, 6.0 <= watchOS < 6.2.9, or 7.0 <= watchOS < 7.1.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped5.3.96.2.97.1
Apply the appropriate Apple security updates (Security Update 2020-006, iOS 14.2, iPadOS 14.2, watchOS updates, or macOS updates) to all affected devices. This is a local privilege escalation vulnerability requiring a malicious application to be already running on the device.
iOS 14.2/iPadOS 14.2, iOS 12.4.9, macOS 11.0.1, macOS 10.15.7 (Security Update 2020-006), watchOS 7.1/6.2.9/5.3.9
- Identify the affected device type (iPhone, iPad, Mac, or Apple Watch)
- For iOS devices: Go to Settings > General > Software Update and install iOS 12.4.9 (for older devices) or iOS 14.2 (for supported devices)
- For iPadOS devices: Go to Settings > General > Software Update and install iPadOS 14.2
- For macOS devices: Go to System Preferences > Software Update and install the available security update (10.15.7, 11.0.1, or the appropriate Security Update 2020-006 for High Sierra/Mojave)
- For Apple Watch: On the iPhone, open the Watch app, go to General > Software Update, and install watchOS 5.3.9, 6.2.9, or 7.1 as applicable
- After updating, verify the device is running the patched version in Settings > General > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-27950 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-27950 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data