Mac Os XOperating system · Apple

CVE-2021-1878

MEDIUM · 6.5 CVSS v3.1 Published 2021-09-08
Fix available
A fix is available. Upgrade to 11.3 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
An integer overflow was addressed with improved input validation. This issue is fixed in macOS Big Sur 11.3, Security Update 2021-002 Catalina, Security Update 2021-003 Mojave. An attacker in a privileged network position may be able to leak sensitive user information.

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 confidence

An integer overflow vulnerability in Apple macOS that could allow an attacker with privileged network position to leak sensitive user information. The vulnerability was addressed through improved input validation in the affected macOS versions.

MitigationApply the relevant macOS security update: Big Sur 11.3, Security Update 2021-002 for Catalina, or Security Update 2021-003 for Mojave.

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
Mac Os XOperating system
Affected:>= 10.14, <= 10.14.5>= 10.15, <= 10.15.5= 10.14.6= 10.15.6= 10.15.7
macOSOperating system
Affected:>= 11.0, < 11.3

CVSS 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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check macOS version
    Run 'sw_vers -productVersion' in Terminal to get the exact macOS version number
    Affected if The version is 10.14.6, 10.15.6, 10.15.7, or any 10.14.x through 10.15.5, or falls between 11.0 and 11.2.x (inclusive)
  2. Verify security update status
    Check System Preferences > Security & Privacy > General for the 'Your computer is up to date' message, or run 'system_profiler SPSoftwareDataType' to see installed security updates
    Affected if No security update from 2021 (such as Security Update 2021-002, 2021-003, or Big Sur 11.3) is installed on vulnerable versions
  3. Identify network exposure
    Review running network services and listeners via 'netstat -an' or System Preferences > Sharing to see which network features are enabled
    Affected if The system has network-facing services enabled and is running a vulnerable macOS version without the security update

A user is affected if they are running any macOS version between 10.14 and 10.15.7, or between 11.0 and 11.2.x, without the corresponding 2021 security updates installed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 11.3 or later
Fixed in 11.3
Interim mitigation

Apply the relevant macOS security update: Big Sur 11.3, Security Update 2021-002 for Catalina, or Security Update 2021-003 for Mojave.

Recommended fix High confidence

macOS Big Sur 11.3+ or apply platform-specific Security Update 2021-002 (Catalina) / 2021-003 (Mojave)

  1. Check current macOS version: Apple menu > About This Mac
  2. If running macOS Big Sur (11.x), upgrade to macOS 11.3 or later via Software Update
  3. If running macOS Catalina (10.15), apply Security Update 2021-002 via Apple menu > System Preferences > Software Update
  4. If running macOS Mojave (10.14), apply Security Update 2021-003 via Apple menu > System Preferences > Software Update
  5. After updating, verify the fix is applied by checking System Preferences > Software Update for no further relevant updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mac Os X Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-1878 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-1878 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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