dbcve.org
ScalaApplication · Jetbrains

CVE-2020-7907

HIGH · 7.5 CVSS v3.1 Published 2020-02-21
Fix available
A fix is available. Upgrade to 2019.2.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
In the JetBrains Scala plugin before 2019.2.1, some artefact dependencies were resolved over unencrypted connections.

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 confidence

The JetBrains Scala plugin before version 2019.2.1 resolved artefact dependencies over unencrypted HTTP connections instead of HTTPS, allowing potential man-in-the-middle attackers to intercept or modify dependency downloads during the build process.

MitigationUpgrade the JetBrains Scala plugin to version 2019.2.1 or later, or ensure all build tool repository configurations use HTTPS URLs exclusively.

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
ScalaApplication
Affected:< 2019.2.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate your JetBrains IDE with Scala plugin
    Open your JetBrains IDE (such as IntelliJ IDEA, PyCharm, or other JetBrains product) that has the Scala plugin installed. Identify the IDE name and version from the About dialog (Help > About on Windows/Linux, or IntelliJ IDEA > About on macOS).
    Affected if The IDE has the Scala plugin installed but you cannot confirm the plugin version below.
  2. Access the Scala plugin version information
    Navigate to Settings > Plugins (or Preferences > Plugins on macOS). In the Marketplace or Installed tab, search for 'Scala'. The plugin details panel or the plugin entry will display the installed version number.
    Affected if The Scala plugin is installed and visible in the plugins list.
  3. Compare the plugin version against the affected range
    Note the installed version number displayed for the Scala plugin. Compare it numerically to version 2019.2.1. Any version lower than 2019.2.1 (such as 2019.2.0, 2019.1.x, etc.) falls within the affected range.
    Affected if The Scala plugin version is lower than 2019.2.1 (for example, 2019.1.4 or 2019.1).

Your environment is affected if the JetBrains Scala plugin version is installed and is below 2019.2.1, as that version and earlier resolve dependencies over unencrypted HTTP connections.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 2019.2.1 or later
Fixed in 2019.2.1
Interim mitigation

Upgrade the JetBrains Scala plugin to version 2019.2.1 or later, or ensure all build tool repository configurations use HTTPS URLs exclusively.

Fix this in Scala Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-7907 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-7907 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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