CYBERSECURITYTRACKER
TRACKING7,457 stories in this site build1,583 vulnerability news stories in this site build
Vulnerabilities

CVE-2022-0540

Review this vulnerability's source-backed evidence, with unavailable values and read failures kept distinct.

A permanent, source-backed tracker page. Values are shown only when returned; explicit gaps and read failures remain different states.

Full record read. Reported values and explicit gaps below come from the tracked record. Tracker data as of: .

Detection and validation

Mapped metadata availability only. These signals do not change priority.

  • Sigma

    Not mapped by tracked sources.

  • Atomic

    Not mapped by tracked sources.

  • Nuclei

    Atlassian Jira Seraph - Authentication Bypass. Check identifier: CVE-2022-0540.

    Open Nuclei metadata

  • Metasploit

    Not mapped by tracked sources.

What it is

Reported

A vulnerability in Jira Seraph allows a remote, unauthenticated attacker to bypass authentication by sending a specially crafted HTTP request. This affects Atlassian Jira Server and Data Center versions before 8.13.18, versions 8.14.0 and later before 8.20.6, and versions 8.21.0 and later before 8.22.0. This also affects Atlassian Jira Service Management Server and Data Center versions before 4.13.18, versions 4.14.0 and later before 4.20.6, and versions 4.21.0 and later before 4.22.0.

Source reported · Source: NVD · Source last published: · Source description excerpt; complete tracked detail loads below. · Source last updated: · Tracker data as of:

What is affected

Reported

Atlassian; Jira Server and Data Center. Product-level identification only; no affected-version conclusion is available from this field.

Source reported · Source: NVD · Source last published: · Source last updated: · Tracker data as of:

Urgency and basis

Reported

Act · 458.2

Tracker computed · Tracker decision tier from the evidence detailed below · Source last updated: · Tracker data as of:

Exploitation evidence

Reported

listed by a tracked exploitation catalog · VulnCheck KEV

Source reported · VulnCheck KEV added: · Source last updated: · Tracker data as of:

What to do

Reported

Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.

Source remediation ↗

Source reported · Tracked source remediation field · Source last updated: · Tracker data as of:

Evidence detail

Loading the full tracker evidence record…

Glossary

Open in glossary