CVE-2023-32370
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 validation. This issue is fixed in macOS Ventura 13.3. Content Security Policy to block domains with wildcards may fail.
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 logic validation flaw in macOS Ventura 13.3 causes Content Security Policy (CSP) to fail to properly enforce wildcard domain restrictions, potentially allowing domains with wildcard patterns to bypass CSP blocking rules.
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>= 13.0, < 13.3< 2.40.1< 2.40.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 macOS versionRun 'sw_vers -productVersion' in Terminal to get the installed macOS version numberAffected if The version is 13.0, 13.1, or 13.2 (versions 13.0.0 through 13.2.x)
-
Check WebKitGTK version on Linux systemsRun 'pkg-config --modversion webkit2gtk-4.1' or 'pkg-config --modversion webkit2gtk-4.0' depending on the API version in useAffected if The version is below 2.40.1 (for 4.1 API) or the equivalent below 2.40.1 for 4.0 API
-
Check WPEWebKit versionRun 'pkg-config --modversion wpewebkit-1.1' or check the package version installed via the system package managerAffected if The version is below 2.40.1
-
Verify CSP is in useInspect web application configurations or check if the affected system serves web content with CSP headers defined using wildcard domain patterns (e.g., *.example.com)Affected if Content Security Policy headers with wildcard domain patterns are configured and the software version is within the affected range
A user is affected if they are running macOS 13.0-13.2, WebKitGTK below 2.40.1, or WPEWebKit below 2.40.1 AND have Content Security Policy configurations using wildcard domain restrictions.
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 · scoped2.40.113.3
Update macOS to version 13.3 or later which contains the corrected domain validation logic for Content Security Policy wildcard matching.
macOS Ventura 13.3+ or Webkitgtk/Wpe WebKit 2.40.1+
- Identify the affected product: macOS Ventura (13.0-13.2), Webkitgtk, or Wpe WebKit
- For macOS users: Open System Settings > General > Software Update and install the macOS Ventura 13.3 update or later
- For Webkitgtk: Update to version 2.40.1 or later via your distribution's package manager (e.g., apt-get update && apt-get upgrade webkit2gtk)
- For Wpe WebKit: Update to version 2.40.1 or later via your distribution's package manager
- After updating, verify the patch was applied by checking the WebKit version or macOS build number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32370 — 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-2023-32370 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