Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

GHSA-wj4j-qc2m-fgh7

MEDIUM

GHSA-wj4j-qc2m-fgh7 is a medium-severity (CVSS 5.3) CWE-427 vulnerability in mattermost-desktop. O3 Security confirms whether GHSA-wj4j-qc2m-fgh7 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Mattermost Desktop App Uncontrolled Search Path Vulnerability

Also known asCVE-2024-39613
Published
Sep 16, 2024
Updated
Sep 16, 2024
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Sep 16, 2024 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

mattermost-desktopnpm
5downloads / week

Description

Mattermost 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.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmmattermost-desktopall versions5.9.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mattermost-desktop. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update mattermost-desktop to 5.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wj4j-qc2m-fgh7 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-wj4j-qc2m-fgh7 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-wj4j-qc2m-fgh7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Mattermost 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.
O3 Security · Impact-Aware SCA

Is GHSA-wj4j-qc2m-fgh7 in your dependencies?

O3 detects GHSA-wj4j-qc2m-fgh7 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-wj4j-qc2m-fgh7: mattermost-desktop… | O3 Security