CVE-2023-34352
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 permissions issue was addressed with improved redaction of sensitive information. This issue is fixed in macOS Ventura 13.4, tvOS 16.5, iOS 16.5 and iPadOS 16.5, watchOS 9.5. An attacker may be able to leak user account emails.
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 permissions issue in Apple operating systems allowed unauthorized access to user account email addresses due to improper redaction of sensitive information. The vulnerability existed in the system's handling of user data where email addresses were not properly protected from leakage.
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< 16.5< 16.5>= 13.0, < 13.4< 16.5< 9.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check iOS or iPadOS versionOpen Settings > General > About and look at the 'Version' fieldAffected if Version number is less than 16.5 (for example, 16.4 or earlier)
-
Check macOS versionClick the Apple menu > About This Mac, or open System Settings > AboutAffected if Version is 13.0 through 13.3.x (13.0, 13.1, 13.2, 13.3.x)
-
Check tvOS versionOpen Settings > General > About and note the version numberAffected if Version is less than 16.5 (for example, 16.4 or earlier)
-
Check watchOS versionOn the watch: Settings > General > About, or on paired iPhone open the Watch app > My Watch > AboutAffected if Version is less than 9.5 (for example, 9.4 or earlier)
You are affected if any of your Apple devices run an OS version that falls within the affected ranges: iOS/iPadOS < 16.5, macOS 13.0-13.3.x, tvOS < 16.5, or watchOS < 9.5.
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 · scoped9.513.416.5
Apply the relevant OS security updates: macOS Ventura 13.4 or later, tvOS 16.5 or later, iOS/iPadOS 16.5 or later, or watchOS 9.5 or later.
iOS 16.5, iPadOS 16.5, macOS Ventura 13.4, tvOS 16.5, watchOS 9.5
- For iPhone or iPad: Go to Settings > General > Software Update and install iOS 16.5 or iPadOS 16.5
- For Mac: Go to System Settings > General > Software Update and install macOS Ventura 13.4
- For Apple TV: Go to Settings > System > Software Updates and install tvOS 16.5
- For Apple Watch: On your iPhone, open the Watch app, go to My Watch > General > Software Update and install watchOS 9.5
- After updating, verify the update was successful by checking the OS version in Settings/About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34352 — 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-34352 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