CVE-2022-22674
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 issue existed that led to the disclosure of kernel memory. This was addressed with improved input validation. This issue is fixed in macOS Monterey 12.3.1, Security Update 2022-004 Catalina, macOS Big Sur 11.6.6. A local user may be able to read kernel memory.
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 local out-of-bounds read vulnerability in macOS allows an unprivileged local user to read kernel memory contents due to insufficient input validation. This information disclosure could potentially aid further privilege escalation attacks.
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.15, < 10.15.7= 10.15.7>= 11.0, < 11.6.6>= 12.0.0, < 12.3.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
- 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.
-
Check installed macOS versionRun 'sw_vers -ProductVersion' in Terminal to retrieve the exact version number of macOSAffected if The version matches 10.15.7, or falls within 11.0 to 11.6.6, or 12.0.0 to 12.3.1
-
Confirm full version stringRun 'sw_vers -ProductVersion' and note both the major.minor.patch (e.g., 12.3) and the build number from 'sw_vers -BuildVersion'Affected if The build version corresponds to an unpatched release within the affected version ranges
-
Verify patch status via system profilerRun 'system_profiler SPSoftwareDataType' and look for the Security Update or macOS version entry in the outputAffected if No Security Update 2022-004 (for Catalina), no macOS 11.6.6 update, or no macOS Monterey 12.3.1 update is listed as installed
A system is affected if it runs macOS 10.15.7, any version from 11.0 through 11.6.5, or any version from 12.0.0 through 12.3.0 without the corresponding security patch installed.
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.15.711.6.612.3.1
Apply the vendor-supplied security updates: macOS Monterey 12.3.1, Security Update 2022-004 for Catalina, or macOS Big Sur 11.6.6 to all affected systems.
macOS Monterey 12.3.1, macOS Big Sur 11.6.6, or Security Update 2022-004 for Catalina
- Open System Preferences (or System Settings on macOS Ventura and later)
- Click on Software Update to check for available updates
- For macOS Monterey (12.x) users: Install macOS Monterey 12.3.1 or later
- For macOS Big Sur (11.x) users: Install macOS Big Sur 11.6.6 or later
- For macOS Catalina (10.15.x) users: Install Security Update 2022-004 Catalina
- Restart the system after the update completes
- Verify the update was successful by checking the macOS version in About This Mac
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22674 — 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-22674 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