Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2020-36239

Jira Data Center, Jira Core Data Center, Jira Software Data Center from version 6.3.0 before 8.5.16, from 8.6.0 before 8.13.8, from 8.14.0…

Description

Jira Data Center, Jira Core Data Center, Jira Software Data Center from version 6.3.0 before 8.5.16, from 8.6.0 before 8.13.8, from 8.14.0 before 8.17.0 and Jira Service Management Data Center from version 2.0.2 before 4.5.16, from version 4.6.0 before 4.13.8, and from version 4.14.0 before 4.17.0 exposed a Ehcache RMI network service which attackers, who can connect to the service, on port 40001 and potentially 40011[0][1], could execute arbitrary code of their choice in Jira through deserialization due to a missing authentication vulnerability. While Atlassian strongly suggests restricting access to the Ehcache ports to only Data Center instances, fixed versions of Jira will now require a shared secret in order to allow access to the Ehcache service. [0] In Jira Data Center, Jira Core Data Center, and Jira Software Data Center versions prior to 7.13.1, the Ehcache object port can be randomly allocated. [1] In Jira Service Management Data Center versions prior to 3.16.1, the Ehcache object port can be randomly allocated.

Timeline

  1. ID reserved

    By atlassian

  2. · 6 months later

    Published

  3. · 3 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2020-36239, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
49.8% · top 1.1% of all CVEs (11 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.

Affected products

  • Atlassian · Jira Data Center

    • affected 6.3.0 – < unspecified
    • affected unspecified – < 8.5.16
    • affected 8.6.0 – < unspecified
    • affected unspecified – < 8.13.8
    • affected 8.14.0 – < unspecified
    • affected unspecified – < 8.17.0
  • Atlassian · Jira Core Data Center

    • affected 6.3.0 – < unspecified
    • affected unspecified – < 8.5.16
    • affected 8.6.0 – < unspecified
    • affected unspecified – < 8.13.8
    • affected 8.14.0 – < unspecified
    • affected unspecified – < 8.17.0
  • Atlassian · Jira Software Data Center

    • affected 6.3.0 – < unspecified
    • affected unspecified – < 8.5.16
    • affected 8.6.0 – < unspecified
    • affected unspecified – < 8.13.8
    • affected 8.14.0 – < unspecified
    • affected unspecified – < 8.17.0
  • Atlassian · Jira Service Management Data Center

    • affected 2.0.2 – < unspecified
    • affected unspecified – < 4.5.16
    • affected 4.6.0 – < unspecified
    • affected unspecified – < 4.13.8
    • affected 4.14.0 – < unspecified
    • affected unspecified – < 4.17.0

References

References3

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2020-36239 badge
[![CVE-2020-36239](https://cveledger.app/badge/CVE-2020-36239.svg)](https://cveledger.app/cve/CVE-2020-36239)

Record last updated .