CVE-2024-39613
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 · uneditedMattermost Desktop App versions <=5.8.0 fail to specify an absolute path when searching the cmd.exe file, which allows a local attacker who is able to put an cmd.exe file in the Downloads folder of a user's machine to cause remote code execution on that 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 · high confidenceThe Mattermost Desktop App versions 5.8.0 and earlier use a relative path when invoking cmd.exe, causing Windows to search the current working directory before the system PATH. An attacker with local access who places a malicious cmd.exe in the user's Downloads folder can achieve arbitrary code execution when the application triggers the vulnerable code path.
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< 5.9.0CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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.
-
Confirm Windows operating systemCheck if the system is running Windows (the vulnerability only affects Windows due to cmd.exe usage). Run 'systeminfo | findstr /B /C:"OS Name"' or check system properties.Affected if Running a non-Windows OS means the vulnerability does not apply.
-
Check installed Mattermost Desktop versionOpen the Mattermost Desktop app, go to Help > About, or right-click the executable (typically in C:\Program Files\Mattermost\ or C:\Users\%USERNAME%\AppData\Local\Programs\mattermost-desktop\) and view Properties > Details to see the version.Affected if Version is 5.8.0 or earlier, or any version below 5.9.0.
-
Verify Downloads folder accessibilityCheck if the Downloads folder (typically C:\Users\%USERNAME%\Downloads\) is writable by other local users or if the system has multi-user access where an attacker could place a file.Affected if The Downloads folder is writable by an attacker who could place a malicious cmd.exe there.
-
Review Mattermost execution behaviorMonitor or inspect the application's process execution using tools like Process Monitor (from Sysinternals) to observe if and when cmd.exe is invoked during normal operation.Affected if The application invokes cmd.exe using relative path resolution, which can be confirmed by observing the command execution behavior.
You are affected if running Windows with Mattermost Desktop version 5.8.0 or earlier where the app uses relative path to invoke cmd.exe, allowing a local attacker who can write to your Downloads folder to execute arbitrary code.
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 · scoped5.9.0
Upgrade Mattermost Desktop App to version 5.9.0 or later, which implements absolute path resolution for system command execution.
5.9.0
- Backup your current Mattermost Desktop installation and user data
- Navigate to the official Mattermost download page at mattermost.com
- Download Mattermost Desktop version 5.9.0 or later for your operating system
- Uninstall the current vulnerable version of Mattermost Desktop
- Install the newly downloaded version 5.9.0 or later
- Launch the application and verify it starts successfully
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-39613 — 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-39613 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