CVE-2023-32360
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 · uneditedAn authentication issue was addressed with improved state management. This issue is fixed in macOS Big Sur 11.7.7, macOS Monterey 12.6.6, macOS Ventura 13.4. An unauthenticated user may be able to access recently printed documents.
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 confidenceThis is an authentication bypass vulnerability in macOS where an unauthenticated user can access recently printed documents. The issue stemmed from improper state management in the print spooling system, allowing access to print job outputs without proper authentication verification.
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>= 11.0, < 11.7.7>= 12.0.0, < 12.6.6>= 13.0, < 13.4CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify macOS versionOpen Terminal and run 'sw_vers -productVersion' to get the exact version number (e.g., 13.3, 12.5, 11.7)Affected if The version falls within < 11.7.7, >= 12.0.0 and < 12.6.6, or >= 13.0 and < 13.4
-
Confirm print spooler is activeCheck if CUPS print service is running by opening System Settings > Printers & Scanners or running 'lpstat -t' in TerminalAffected if Print services have been configured or used on the system, as the vulnerability allows access to recently printed documents through the spooling system
-
Review print job accessibilityCheck the /var/spool/cups directory permissions and recent job files using 'ls -la /var/spool/cups/'Affected if The directory is accessible without authentication, which would indicate the vulnerable condition exists
You are affected if running any macOS version 11.0-11.7.6, 12.0-12.5.5, or 13.0-13.3 and the print spooling system is or has been used on the machine.
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 · scoped11.7.712.6.613.4
Apply the vendor-supplied macOS security updates: version 11.7.7 for Big Sur, 12.6.6 for Monterey, or 13.4 for Ventura.
macOS Big Sur 11.7.7 / macOS Monterey 12.6.6 / macOS Ventura 13.4 (depending on which major version is currently installed)
- Determine the currently installed macOS version by clicking the Apple menu and selecting About This Mac
- If running macOS Big Sur 11.x, upgrade to version 11.7.7 or later
- If running macOS Monterey 12.x, upgrade to version 12.6.6 or later
- If running macOS Ventura 13.x, upgrade to version 13.4 or later
- To upgrade, go to System Settings > General > Software Update and install the available security update
- Restart the Mac when prompted to complete the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32360 — 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-32360 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