CVE-2024-23742
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 issue in Loom on macOS version 0.196.1 and before, allows remote attackers to execute arbitrary code via the RunAsNode and enableNodeClilnspectArguments settings. NOTE: the vendor disputes this because it requires local access to a victim's machine.
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 confidenceLoom for macOS versions 0.196.1 and earlier expose RunAsNode and enableNodeCliInspectArguments settings that can be manipulated to execute arbitrary code. These are Node.js runtime flags where RunAsNode affects how the Electron/Node process behaves and enableNodeCliInspectArguments controls debugging inspect arguments, potentially allowing an attacker to spawn a Node process with elevated privileges or remote debugging that leads to code execution.
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<= 0.196.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 if Loom is installedLook for Loom in the Applications folder: ls /Applications/ | grep -i loom, or check via Spotlight (Cmd+Space) searching for 'Loom'Affected if Loom application exists on the system
-
Determine Loom versionRight-click Loom in Applications > Get Info, or run: defaults read /Applications/Loom.app/Contents/Info CFBundleShortVersionStringAffected if Version is 0.196.1 or earlier
-
Locate Loom configuration filesCheck for config files in ~/Library/Application Support/Loom/, ~/Library/Preferences/com.loom.desktop.plist, or similar locations within the user's Library folderAffected if Configuration files exist and are writable by the user
-
Inspect for RunAsNode settingSearch configuration files for 'RunAsNode' or 'runasnode' entries: grep -r 'RunAsNode' ~/Library/Application\ Support/Loom/ 2>/dev/nullAffected if RunAsNode setting is present and enabled (set to true or 1)
-
Inspect for enableNodeCliInspectArguments settingSearch configuration files for 'enableNodeCliInspectArguments' or similar inspect-related flags: grep -r 'enableNodeCliInspectArguments\|inspect\|debug' ~/Library/Application\ Support/Loom/ 2>/dev/nullAffected if enableNodeCliInspectArguments is present and enabled, or debugging flags are exposed in config
User is affected if Loom version 0.196.1 or earlier is installed AND configuration files contain exposed RunAsNode or enableNodeCliInspectArguments settings that could be manipulated.
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.
From vendor dataUpdate Loom to a version beyond 0.196.1 where these settings are properly secured. Until then, restrict local machine access and ensure no untrusted users have write access to Loom configuration files.
- 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-23742 — 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-23742 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