CVE-2024-44128
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 adding an additional prompt for user consent. This issue is fixed in macOS Sequoia 15, macOS Sonoma 14.7, macOS Ventura 13.7. An Automator Quick Action workflow may be able to bypass Gatekeeper.
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 · high confidenceAn Automator Quick Action workflow could bypass Gatekeeper checks, allowing code to execute without the normal code signing and notarization requirements. The vulnerability was fixed by adding an additional user consent prompt before the workflow runs.
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< 13.7>= 14.0, < 14.7CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 versionGo to Apple menu > About This Mac, or run 'sw_vers' in Terminal. Note the full version number (e.g., 14.6, 13.6, etc.).Affected if The version is 14.0 through 14.6, or 13.0 through 13.6 (below 13.7)
-
Confirm Automator Quick Action presenceNavigate to ~/Library/Services/ or /Library/Services/ and look for .workflow files. In Automator, open a workflow and check if it is saved as a Quick Action.Affected if Quick Action workflows exist in the user's Services folder or system-wide Services folder
-
Verify Gatekeeper is enabledRun 'spctl --status' in Terminal to check if Gatekeeper is enforcing code execution restrictions.Affected if Gatekeeper is disabled (status shows 'assessments disabled') or the status cannot be verified
You are affected if your macOS version is 13.7 or later (for Ventura) or 14.7 or later (for Sonoma), otherwise the Automator Quick Action bypasses Gatekeeper protections.
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 · scoped13.714.7
Apply the vendor-supplied macOS updates (Ventura 13.7, Sonoma 14.7, or Sequoia 15) to enforce the new consent prompt and restore Gatekeeper protection for Automator workflows.
macOS 13.7 (Ventura), macOS 14.7 (Sonoma), or macOS 15 (Sequoia)
- Back up your Mac using Time Machine or another backup method before proceeding with the system update
- Check your current macOS version by clicking the Apple menu and selecting About This Mac
- For macOS Ventura (13.x) users: Upgrade to macOS 13.7 by going to System Settings > General > Software Update and installing the available update
- For macOS Sonoma (14.x) users: Upgrade to macOS 14.7 by going to System Settings > General > Software Update and installing the available update
- Alternatively, download macOS 15 (Sequoia) from the Mac App Store for the latest version with all security fixes
- After upgrading, verify the fix is applied by checking About This Mac to confirm you are running a fixed version (13.7, 14.7, or 15.0)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-44128 — 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-44128 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