dbcve.org
BitbucketApplication · Atlassian

CVE-2020-14171

MEDIUM · 6.5 CVSS v3.1 Published 2020-07-09
Fix available
A fix is available. Upgrade to 7.2.4 or later.
See remediation →
74/100
Remediation priority · Elevated
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
Atlassian Bitbucket Server from version 4.9.0 before version 7.2.4 allows remote attackers to intercept unencrypted repository import requests via a Man-in-the-Middle (MITM) attack.

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

Atlassian Bitbucket Server versions 4.9.0 through 7.2.3 do not encrypt repository import requests, enabling attackers with MITM positioning on the network path to intercept and read sensitive repository data during the import process.

MitigationUpgrade to Bitbucket Server 7.2.4 or later. As an interim measure, ensure all repository import operations occur over TLS-encrypted network paths or within a VPN tunnel.

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
BitbucketApplication
Affected:>= 4.9.0, < 7.2.4

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/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. Identify Bitbucket Server version
    Check the Bitbucket instance version by accessing the /rest/api/1.0/application-properties endpoint or viewing the footer of the Bitbucket administration console
    Affected if The installed version is 4.9.0 through 7.2.3 inclusive (versions >= 4.9.0 and < 7.2.4 are vulnerable)
  2. Confirm repository import capability is available
    Verify that the Bitbucket Server instance has repository import functionality enabled (typically accessible via the admin UI under 'Repositories' > 'Import repository' or the REST API at /rest/api/1.0/repos/import)
    Affected if Repository import feature is enabled and accessible on the instance
  3. Check for historical import operations
    Review Bitbucket Server audit logs or database records for past repository import operations (look for events of type 'REPO_IMPORT' or similar)
    Affected if Repository imports have been performed on this instance while running a vulnerable version

You are affected if your Bitbucket Server version is 4.9.0 through 7.2.3 and repository import operations have been performed on your network without additional encryption wrapping.

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 7.2.4 or later
Fixed in 7.2.4
Interim mitigation

Upgrade to Bitbucket Server 7.2.4 or later. As an interim measure, ensure all repository import operations occur over TLS-encrypted network paths or within a VPN tunnel.

Fix this in Bitbucket Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-14171 — 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-14171 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