CVE-2020-1976
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 denial-of-service (DoS) vulnerability in Palo Alto Networks GlobalProtect software running on Mac OS allows authenticated local users to cause the Mac OS kernel to hang or crash. This issue affects GlobalProtect 5.0.5 and earlier versions of GlobalProtect 5.0 on Mac OS.
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 · moderate confidenceA local denial-of-service vulnerability in Palo Alto Networks GlobalProtect client software versions 5.0.5 and earlier on Mac OS allows an authenticated local user to trigger a kernel hang or crash, completely impacting system availability.
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>= 5.0, <= 5.0.5CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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.
-
Verify GlobalProtect is installed on Mac OSCheck for the presence of GlobalProtect.app in /Applications directory using: ls -la /Applications/ | grep -i GlobalProtectAffected if GlobalProtect.app is not found in /Applications, the vulnerability does not apply
-
Identify installed GlobalProtect version on MacOpen GlobalProtect.app, navigate to the app's Info window (Cmd+I in Finder), or run: defaults read /Applications/GlobalProtect.app/Contents/Info.plist CFBundleShortVersionStringAffected if No version information is returned or the application is not installed
-
Compare version against affected rangeCompare the installed version number to the affected range: 5.0 through 5.0.5 (inclusive)Affected if Installed version is 5.0, 5.0.1, 5.0.2, 5.0.3, 5.0.4, or 5.0.5, indicating the environment is affected by this CVE
-
Confirm OS is Mac OSVerify the operating system is macOS by checking System Preferences or running: uname -sAffected if The operating system is not macOS (e.g., Windows or Linux), as this specific vulnerability affects only macOS endpoints
A Mac OS system with GlobalProtect version 5.0 through 5.0.5 installed is affected by this vulnerability; version 5.0.6 or later, or absence of GlobalProtect, indicates the system is not affected.
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.
From vendor dataUpgrade GlobalProtect to a version later than 5.0.5 on all Mac OS endpoints to remediate this vulnerability.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-1976 — 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-1976 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