CVE-2021-30823
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 logic issue was addressed with improved restrictions. This issue is fixed in macOS Monterey 12.0.1, iOS 14.8 and iPadOS 14.8, tvOS 15, Safari 15, watchOS 8. An attacker in a privileged network position may be able to bypass HSTS.
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 confidenceCVE-2021-30823 is a logic flaw in Apple's HSTS (HTTP Strict Transport Security) implementation that allows an attacker with privileged network position (e.g., man-in-the-middle) to bypass HSTS protections. This enables the attacker to downgrade HTTPS connections to HTTP, exposing sensitive traffic. The vulnerability affects macOS Monterey 12.0.1 and earlier, iOS/iPadOS 14.8 and earlier, tvOS 15 and earlier, Safari 15 and earlier, and watchOS 8 and earlier.
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< 15.0.0< 14.8< 14.8< 12.0.1< 15.0< 8.0CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Apple device and operating systemDetermine whether the device is a Mac, iPhone/iPad, Apple TV, or Apple Watch. On Mac, go to Apple menu > About This Mac. On iPhone/iPad, go to Settings > General > About. On Apple TV, go to Settings > General > About. On Apple Watch, open the Watch app on iPhone and go to General > About.Affected if Device runs any of the affected Apple operating systems listed below
-
Check macOS version on Mac computersOpen Terminal and run: sw_vers -productVersion. Alternatively, go to Apple menu > About This Mac and note the version number (e.g., 12.0, 11.6, etc.).Affected if Version is lower than 12.0.1 (e.g., 12.0, 11.x, 10.x)
-
Check iOS or iPadOS version on iPhone or iPadGo to Settings > General > About and note the version number displayed next to 'Version' (e.g., 14.7, 14.6, etc.).Affected if Version is lower than 14.8 (e.g., 14.7, 14.6, 13.x, etc.)
-
Check Safari version on macOSOpen Safari, go to Safari menu > About Safari. The version number appears in the window that opens (e.g., 14.1.2, 15.0, etc.).Affected if Version is lower than 15.0.0 (e.g., 14.1.2, 14.0, 13.x)
-
Check tvOS version on Apple TVGo to Settings > General > About and note the version number (e.g., 14.7, 14.6, etc.).Affected if Version is lower than 15.0 (e.g., 14.7, 14.6, 13.x)
-
Check watchOS version on Apple WatchOn Apple Watch, go to Settings > General > About and note the version. Alternatively, open the Watch app on paired iPhone, go to General > About, and check the watchOS version.Affected if Version is lower than 8.0 (e.g., 7.6, 7.5, 6.x, etc.)
The environment is affected if any installed Apple operating system or Safari version falls below the thresholds: macOS 12.0.1, iOS/iPadOS 14.8, tvOS 15.0, watchOS 8.0, or Safari 15.0.0.
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 · scoped8.012.0.114.8
Apply the vendor-supplied patches: update to macOS Monterey 12.0.1+, iOS/iPadOS 14.8+, tvOS 15+, Safari 15+, and watchOS 8+ as appropriate for each affected device.
macOS Monterey 12.0.1, iOS 14.8, iPadOS 14.8, tvOS 15.0, watchOS 8.0, Safari 15
- For macOS users: Update to macOS Monterey 12.0.1 via System Preferences > Software Update
- For iPhone users: Update to iOS 14.8 via Settings > General > Software Update
- For iPad users: Update to iPadOS 14.8 via Settings > General > Software Update
- For Apple TV users: Update to tvOS 15.0 via Settings > System > Software Updates
- For Apple Watch users: Update to watchOS 8.0 via the Watch app on iPhone > General > Software Update
- For Safari: Update via macOS update (Safari 15 is included in macOS Monterey 12.0.1)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30823 — 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-2021-30823 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