CVE-2022-22664
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 out-of-bounds read was addressed with improved bounds checking. This issue is fixed in Logic Pro 10.7.3, GarageBand 10.4.6, macOS Monterey 12.3. Opening a maliciously crafted file may lead to unexpected application termination or arbitrary code execution.
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 confidenceAn out-of-bounds read vulnerability in Logic Pro, GarageBand, and macOS Monterey allows arbitrary code execution or application termination when processing a maliciously crafted file. The issue was addressed through improved bounds checking in the affected applications.
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< 10.4.6< 10.7.3< 12.3CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 GarageBand versionOpen GarageBand from /Applications, then click the GarageBand menu and select 'About GarageBand' to view the version numberAffected if Version is lower than 10.4.6 and you open audio files from untrusted sources
-
Check Logic Pro X versionOpen Logic Pro X from /Applications, then click the Logic Pro menu and select 'About Logic Pro X' to view the version numberAffected if Version is lower than 10.7.3 and you open project files from untrusted sources
-
Check macOS versionClick the Apple menu in the top-left corner and select 'About This Mac' to view the macOS versionAffected if macOS version is lower than 12.3 and you use GarageBand or Logic Pro X
You are affected if any of GarageBand is below 10.4.6, Logic Pro X is below 10.7.3, or macOS is below 12.3, and you open files from untrusted sources in these applications.
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 · scoped10.4.610.7.312.3
Update to Logic Pro 10.7.3, GarageBand 10.4.6, or macOS Monterey 12.3 or later. Avoid opening files from untrusted sources.
GarageBand 10.4.6, Logic Pro X 10.7.3, macOS Monterey 12.3
- Open the Mac App Store application on your macOS device
- Click on the 'Updates' tab in the Mac App Store
- Locate GarageBand and/or Logic Pro X in the list of available updates
- Click 'Update' next to each application to install the latest version
- Alternatively, visit support.apple.com and download the latest versions of GarageBand (10.4.6 or later) and Logic Pro X (10.7.3 or later)
- For macOS itself, go to System Preferences > Software Update and install macOS Monterey 12.3 or later
- Restart your Mac after applying macOS updates to ensure all components are properly updated
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-2022-22664 — 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-2022-22664 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