CVE-2020-11685
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 GoLand before 2019.3.2, the plugin repository was accessed via HTTP instead of HTTPS.
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 plugin repository in JetBrains GoLand before version 2019.3.2 was accessed via unencrypted HTTP instead of HTTPS, allowing man-in-the-middle attackers to intercept and potentially modify plugin downloads during transit.
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< 2019.3.2CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 GoLand versionOpen GoLand, go to Help > About (or on macOS, GoLand > About). The version number is displayed in the dialog that appears.Affected if The version shown is earlier than 2019.3.2 (for example, 2019.3, 2019.2, 2019.1, etc.)
-
Verify plugin repository configuration uses HTTPCheck the plugin settings file or network configuration. On Windows, this may be in the GoLand config directory (typically %APPDATA%\JetBrains\GoLand<version>\plugins\). Look for plugin repository URLs configured with http:// instead of https://.Affected if The plugin repository URL is configured to use unencrypted HTTP (http://) rather than HTTPS (https://)
-
Inspect network traffic during plugin downloadUse a network monitoring tool (such as Wireshark or browser developer tools) to capture network traffic while downloading a plugin from the GoLand plugin repository.Affected if Traffic to the plugin repository travels over unencrypted HTTP (port 80) rather than HTTPS (port 443)
You are affected if you are running GoLand versions earlier than 2019.3.2 AND your plugin downloads traverse unencrypted HTTP connections.
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 data2019.3.2
Upgrade to GoLand 2019.3.2 or later, which implements HTTPS for plugin repository communications.
- Consultation0.5 h
- Implementation0.5 h
- Testing0.5 h
- Review / QA0.3 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-2020-11685 — 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-11685 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