dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 21 Oct 2022.
BitbucketApplication · Atlassian

CVE-2022-36804

HIGH · 8.8 CVSS v3.1 Published 2022-08-25
Fix available
A fix is available. Upgrade to 7.6.17 / 7.17.10 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable Zero-click Patch available

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
Multiple API endpoints in Atlassian Bitbucket Server and Data Center 7.0.0 before version 7.6.17, from version 7.7.0 before version 7.17.10, from version 7.18.0 before version 7.21.4, from version 8.0.0 before version 8.0.3, from version 8.1.0 before version 8.1.3, and from version 8.2.0 before version 8.2.2, and from version 8.3.0 before 8.3.1 allows remote attackers with read permissions to a public or private Bitbucket repository to execute arbitrary code by sending a malicious HTTP request. This vulnerability was reported via our Bug Bounty Program by TheGrandPew.

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

Multiple API endpoints in Atlassian Bitbucket Server and Data Center contain a command injection vulnerability. Attackers with read permissions to any public or private repository can send malicious HTTP requests to these API endpoints, allowing execution of arbitrary code on the affected server.

MitigationUpgrade Bitbucket Server/Data Center to version 7.6.17, 7.17.10, 7.21.4, 8.0.3, 8.1.3, 8.2.2, or 8.3.1 or later. If immediate patching is not possible, restrict network access to Bitbucket instances and review API endpoint exposure.

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:>= 7.0.0, < 7.6.17>= 7.7.0, < 7.17.10>= 7.18.0, < 7.21.4>= 8.0.0, < 8.0.3>= 8.1.0, < 8.1.3>= 8.2.0, < 8.2.2= 8.3.0

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

CVSS:3.1/AV:N/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 checks

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

  1. Check installed Bitbucket version
    Log into Bitbucket as an administrator, navigate to Administration > Server Settings > Application info, or query the /rest/api/1.0/application-properties endpoint
    Affected if The version falls within any of these ranges: 7.0.0-7.6.16, 7.7.0-7.17.9, 7.18.0-7.21.3, 8.0.0-8.0.2, 8.1.0-8.1.2, 8.2.0-8.2.1, or 8.3.0
  2. Verify API access is enabled
    Confirm the Bitbucket REST API is accessible by making a GET request to /rest/api/1.0/application-properties or checking that API access is not disabled in Administration > Server Settings
    Affected if The REST API is accessible without additional authentication restrictions beyond standard Bitbucket authentication
  3. Check for exposed API endpoints
    Test access to vulnerable endpoints such as /rest/api/1.0/projects/{project}/repos/{repo}/archive with specially crafted parameters, or review access logs for requests to /rest/api/1.0/repositories/ endpoints with archive or bundle parameters
    Affected if These API endpoints respond to authenticated users with read-level permissions
  4. Review anonymous access setting
    Navigate to Administration > Server Settings > Authentication and check if Anonymous access is enabled, or inspect the bitbucket.properties configuration file for the feature.anonymous.access.enabled setting
    Affected if Anonymous access is enabled, allowing unauthenticated attackers potential exposure to the vulnerable endpoints

Your environment is affected if Bitbucket Server or Data Center is running any version from 7.0.0 through 7.21.3, 8.0.0 through 8.2.1, or 8.3.0, and the REST API is accessible to users with repository read permissions.

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.

dbcve · scoped
Upgrade available Upgrade to 7.6.17 / 7.17.10 / 7.21.4 or later
Fixed in 7.6.177.17.107.21.4
Vendor patch jira.atlassian.com →
Interim mitigation

Upgrade Bitbucket Server/Data Center to version 7.6.17, 7.17.10, 7.21.4, 8.0.3, 8.1.3, 8.2.2, or 8.3.1 or later. If immediate patching is not possible, restrict network access to Bitbucket instances and review API endpoint exposure.

Recommended fix High confidence

Upgrade to 7.6.17, 7.17.10, 7.21.4, 8.0.3, 8.1.3, 8.2.2, or 8.3.1 (or later) depending on your current major version branch

  1. 1. Identify current Bitbucket version by checking the administration console or running `bitbucket-version.sh`
  2. 2. Review Atlassian upgrade documentation and release notes for the target version
  3. 3. Create a complete backup of the Bitbucket home directory and database
  4. 4. Schedule a maintenance window as upgrades require downtime
  5. 5. Download the appropriate fixed version from Atlassian (e.g., from https://www.atlassian.com/software/bitbucket/download-archives)
  6. 6. Stop the Bitbucket service
  7. 7. Run the installer for the target fixed version
  8. 8. Start the Bitbucket service and verify it starts successfully
Caveat Review Atlassian release notes for breaking changes between your current version and target version; major version upgrades may require migration steps

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Bitbucket Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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