CVE-2021-30005
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 · uneditedIn JetBrains PyCharm before 2020.3.4, local code execution was possible because of insufficient checks when getting the project from VCS.
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 confidenceIn JetBrains PyCharm before 2020.3.4, the IDE's functionality for retrieving projects from Version Control Systems (VCS) contained insufficient validation checks, allowing attackers to achieve local code execution on the developer's machine by exploiting how the IDE processes project data from VCS repositories.
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< 2020.3.4CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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.
-
Identify installed PyCharm versionOpen PyCharm and go to Help > About, or run 'pycharm --version' from command line if available. Alternatively, check the installation directory for version information.Affected if The version shown is earlier than 2020.3.4 (for example, 2020.3.3, 2020.3.2, 2020.2.x, etc.)
-
Verify VCS integration is enabledCheck if the Version Control Integration plugin or feature is active in PyCharm. Look under Settings > Version Control to see if any VCS repositories are configured.Affected if VCS integration is enabled and configured with any repository URLs
-
Inspect recent VCS checkout activityLook for recent projects cloned via Get from Version Control (VCS). Check the PyCharm configuration directory (typically in ~/PyCharm* or ~/.PyCharm*) for recent project history files.Affected if Projects were recently retrieved using Get from Version Control with a repository URL
-
Review custom VCS repository configurationsExamine any custom VCS settings or hooks configured in PyCharm. Check Settings > Version Control > Git or other VCS for unusual repository URLs or hook scripts.Affected if Non-standard or untrusted repository URLs are configured in the VCS settings
You are affected if PyCharm version is earlier than 2020.3.4 AND the VCS/Get from Version Control feature has been used with any repository.
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 data2020.3.4
Upgrade PyCharm to version 2020.3.4 or later. Until upgraded, avoid using the VCS/Get from Version Control feature with untrusted or unfamiliar repositories.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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-2021-30005 — 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-2021-30005 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