CVE-2024-23755
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 · uneditedClickUp Desktop before 3.3.77 on macOS and Windows allows code injection because of specific Electron Fuses. There is inadequate protection against code injection through settings such as RunAsNode.
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 confidenceClickUp Desktop versions before 3.3.77 on macOS and Windows contain insecure Electron Fuses configurations that allow code injection. Specifically, the RunAsNode setting is not adequately protected, enabling attackers to execute arbitrary code by manipulating Electron runtime settings.
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< 3.3.77CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 installed ClickUp Desktop versionOn Windows, right-click the ClickUp executable, select Properties, and view the File Version. On macOS, right-click ClickUp in Applications, select Get Info, and view the Version number. Alternatively, check Help > About in the app.Affected if The version shown is less than 3.3.77
-
Verify Electron RunAsNode fuse configurationExamine the ClickUp Desktop executable binary for Electron Fuses settings. This requires checking the compiled Electron binary (typically named ClickUp.exe on Windows or ClickUp on macOS within the app bundle) using an Electron Fuses inspection tool or by analyzing the binary's fuse configuration flags.Affected if The RunAsNode fuse is enabled/not properly disabled in the Electron binary configuration
A user is affected if their installed ClickUp Desktop version is below 3.3.77 AND the Electron RunAsNode fuse is not properly protected, allowing potential code injection through Electron runtime manipulation.
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 · scoped3.3.77
Update ClickUp Desktop to version 3.3.77 or later to obtain the patched Electron Fuses configuration. Verify all client installations are updated across the organization.
ClickUp Desktop version 3.3.77 or later
- Open the ClickUp Desktop application
- Navigate to the application menu (ClickUp dropdown or settings)
- Check the current version under 'About ClickUp' or 'Settings > General'
- If version is below 3.3.77, download the latest version from the official ClickUp website (clickup.com/downloads) or use the in-app update mechanism
- Install the updated version (3.3.77 or later)
- Restart the application to ensure the update is fully applied
- Verify the installed version is 3.3.77 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23755 — 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-23755 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