basicsecurity.net
Proof, not just disclosure.
Threats / Atlassian / CVE-2022-36804
CVE-2022-36804 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Atlassian Bitbucket Server and Data Center vulnerability

Atlassian Bitbucket Server and Data Center contain command injection vulnerabilities in API endpoints that allow authenticated repository users to execute arbitrary code via malicious HTTP requests.

Verdict

Today item — known-exploited.

An attacker with read access to a Bitbucket repository can inject OS commands through API endpoints, achieving remote code execution on the affected server. This enables full system compromise and data exfiltration.

CISA KEV Yes · 2022-09-303EPSS 0.99174 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
92 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-09-30).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.99174 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Atlassian, Bitbucket Server and Data Center. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-78 OS Command Injection, CWE-88 Argument Injection, CWE-158 CWE-158 — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious HTTP request targeting a vulnerable API endpoint in Bitbucket.
Business
The organization's source code repository and development infrastructure are exposed to unauthorized access.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I inject shell metacharacters into request parameters to break out of intended command context.
Business
Attackers gain code execution privileges equivalent to the Bitbucket service account.
3

Lateral reach — past segmentation narrative 3

Attacker
I execute arbitrary OS commands on the server to establish persistence and lateral movement.
Business
The entire development pipeline and connected systems become compromised, enabling supply chain attacks.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 92 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by atlassian (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by atlassianCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.