CVE-2024-54490
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 · uneditedThis issue was addressed by enabling hardened runtime. This issue is fixed in macOS Sequoia 15.2. A local attacker may gain access to user's Keychain items.
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 attacker with macOS access can bypass security controls to read Keychain items. The vulnerability was addressed by enabling hardened runtime, a macOS security feature that enforces code signing and runtime protections.
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< 15.2CVSS 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 macOS versionRun 'sw_vers -productVersion' in TerminalAffected if Version is below 15.2 (e.g., 15.1, 14.x, 13.x, etc.)
-
Identify applications accessing KeychainReview installed applications that handle credentials, passwords, or sensitive data (e.g., browsers, email clients, password managers)Affected if Any such application is in use on an unpatched macOS version
-
Verify hardened runtime status for suspect applicationsRun 'codesign -dvvv /path/to/application.app 2>&1' and look for 'Hardened Runtime = Yes' in the outputAffected if The application shows 'Hardened Runtime = No' or lacks this line entirely (vulnerable configuration)
-
Check code signing validityRun 'codesign --verify --verbose=2 /path/to/application.app' to verify code signature statusAffected if Application fails verification or shows invalid/detached signature, indicating security controls may be weakened
User is affected if running macOS below 15.2 AND applications that access Keychain have hardened runtime disabled or code signing issues.
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 · scoped15.2
Apply macOS Sequoia 15.2 or later security updates. For legacy systems, enable hardened runtime in the affected application's configuration and ensure proper code signing.
macOS Sequoia 15.2
- Back up your Mac using Time Machine or another backup method before upgrading
- Verify application compatibility with macOS Sequoia 15.2
- Open System Settings > General > Software Update
- Install macOS Sequoia 15.2 or later
- Restart your Mac when prompted to complete the installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-54490 — 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-2024-54490 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