CompanionApplication · Atlassian
CVE-2020-4019
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 · uneditedThe file editing functionality in the Atlassian Companion App before version 1.0.0 allows local attackers to have the app run a different executable in place of the app's cmd.exe via a untrusted search path vulnerability.
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 Atlassian Companion App before version 1.0.0 contains an untrusted search path vulnerability in its file editing functionality. The application executes cmd.exe without specifying the full path, allowing local attackers to place a malicious executable in a directory that precedes the legitimate system32 path in the Windows search order, causing the app to execute the attacker's code instead of the genuine Windows command interpreter.
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
CompanionApplication
< 1.0.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.
-
Identify if Atlassian Companion is installedCheck for the presence of Atlassian Companion on the system. Look for installation directories such as C:\Program Files\Atlassian\ or check for the executable 'Atlassian Companion.exe' in typical installation locations.Affected if Atlassian Companion is found on the system
-
Determine the installed versionRight-click on the Atlassian Companion executable, select Properties, and view the File Version on the Details tab. Alternatively, open the app and check About or Help for version information.Affected if The installed version is lower than 1.0.0 (e.g., 0.x.x series)
-
Check directory permissions on the application folderRight-click the Atlassian Companion installation folder, select Properties, go to the Security tab, and review which users have Write or Modify permissions. Check if standard users or unprivileged accounts can write files to these directories.Affected if Users without administrative privileges can write to directories in the application's search path
-
Inspect for suspicious cmd.exe in application directoriesSearch the Atlassian Companion installation directory and any directories in its PATH for unexpected cmd.exe files. Use 'dir /s C:\*cmd.exe' limited to the app directory or use a file integrity checker to enumerate cmd.exe in those locations.Affected if An unexpected cmd.exe is found in a directory that precedes system32 in the search order
A user is affected if Atlassian Companion version below 1.0.0 is installed AND the application directory or any directory in its PATH is writable by untrusted users, allowing injection of a malicious cmd.exe.
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 data1.0.0
Upgrade to Atlassian Companion App version 1.0.0 or later. As a compensating control, ensure the application runs from directories with restricted write permissions to prevent attackers from placing malicious executables in the search path.
Fix this in Companion
Scoped from the published advisory
- 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-2020-4019 — 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-2020-4019 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