Mac Os XOperating system · Apple

CVE-2021-30696

MEDIUM · 5.9 CVSS v3.1 Published 2021-09-08
Fix available
A fix is available. Upgrade to 11.4 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges 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 attacker in a privileged network position may be able to misrepresent application state. This issue is fixed in macOS Big Sur 11.4, Security Update 2021-003 Catalina, Security Update 2021-004 Mojave. A logic issue was addressed with improved state management.

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

A logic flaw in macOS (Catalina, Mojave, Big Sur) allows an attacker with privileged network position to misrepresent application state through improper state management. The vulnerability stems from inadequate handling of application or connection state validation.

MitigationApply the appropriate macOS security update: Big Sur 11.4, Security Update 2021-003 for Catalina, or Security Update 2021-004 for Mojave. Prioritize systems exposed to untrusted network segments.

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.6= 10.14.6= 10.15.7
macOSOperating system
Affected:>= 11.0, < 11.4

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/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 installed macOS version
    Go to Apple menu > About This Mac, or run 'sw_vers' in Terminal
    Affected if Version is 10.14.x through 10.14.5, 10.14.6, 10.15.x through 10.15.6, 10.15.7, or 11.0-11.3 (any version below 11.4 on Big Sur)
  2. Identify network exposure
    Review network configuration: check if the system is directly exposed to untrusted networks, serves as a VPN endpoint, or uses public/unsecured Wi-Fi without firewall protection
    Affected if System has direct network exposure to untrusted or hostile network segments
  3. Verify security update status
    Check System Preferences > Software Update for available updates, or run 'defaults read /Library/Preferences/com.apple.SoftwareUpdate.plist' to inspect last update timestamp
    Affected if No security update (2021-003 for Catalina, 2021-004 for Mojave, or 11.4 for Big Sur) has been installed

System is affected if running any macOS version in the 10.14-10.14.6, 10.15-10.15.7, or 11.0-11.3 range and has network exposure that allows an attacker to occupy a privileged position in the network path.

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.4 or later
Fixed in 11.4
Interim mitigation

Apply the appropriate macOS security update: Big Sur 11.4, Security Update 2021-003 for Catalina, or Security Update 2021-004 for Mojave. Prioritize systems exposed to untrusted network segments.

Recommended fix High confidence

macOS Big Sur 11.4+ | Security Update 2021-003 (Catalina) | Security Update 2021-004 (Mojave)

  1. Open System Preferences (or System Settings on macOS 11+)
  2. Click on 'Software Update' to check for available updates
  3. Install the latest security update: For macOS Big Sur (11.x): upgrade to 11.4 or later; For macOS Catalina (10.15): install Security Update 2021-003; For macOS Mojave (10.14): install Security Update 2021-004
  4. Restart the system when prompted to complete the update

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

Fix this in Mac Os X Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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