gsd-2020-36239
Vulnerability from gsd
Modified
2023-12-13 01:21
Details
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.
Aliases
Aliases
{ "GSD": { "alias": "CVE-2020-36239", "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.", "id": "GSD-2020-36239" }, "gsd": { "metadata": { "exploitCode": "unknown", "remediation": "unknown", "reportConfidence": "confirmed", "type": "vulnerability" }, "osvSchema": { "aliases": [ "CVE-2020-36239" ], "details": "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.", "id": "GSD-2020-36239", "modified": "2023-12-13T01:21:55.668975Z", "schema_version": "1.4.0" } }, "namespaces": { "cve.org": { "CVE_data_meta": { "ASSIGNER": "security@atlassian.com", "DATE_PUBLIC": "2021-07-21T17:00:00", "ID": "CVE-2020-36239", "STATE": "PUBLIC" }, "affects": { "vendor": { "vendor_data": [ { "product": { "product_data": [ { "product_name": "Jira Data Center", "version": { "version_data": [ { "version_affected": "\u003e=", "version_value": "6.3.0" }, { "version_affected": "\u003c", "version_value": "8.5.16" }, { "version_affected": "\u003e=", "version_value": "8.6.0" }, { "version_affected": "\u003c", "version_value": "8.13.8" }, { "version_affected": "\u003e=", "version_value": "8.14.0" }, { "version_affected": "\u003c", "version_value": "8.17.0" } ] } }, { "product_name": "Jira Core Data Center", "version": { "version_data": [ { "version_affected": "\u003e=", "version_value": "6.3.0" }, { "version_affected": "\u003c", "version_value": "8.5.16" }, { "version_affected": "\u003e=", "version_value": "8.6.0" }, { "version_affected": "\u003c", "version_value": "8.13.8" }, { "version_affected": "\u003e=", "version_value": "8.14.0" }, { "version_affected": "\u003c", "version_value": "8.17.0" } ] } }, { "product_name": "Jira Software Data Center", "version": { "version_data": [ { "version_affected": "\u003e=", "version_value": "6.3.0" }, { "version_affected": "\u003c", "version_value": "8.5.16" }, { "version_affected": "\u003e=", "version_value": "8.6.0" }, { "version_affected": "\u003c", "version_value": "8.13.8" }, { "version_affected": "\u003e=", "version_value": "8.14.0" }, { "version_affected": "\u003c", "version_value": "8.17.0" } ] } }, { "product_name": "Jira Service Management Data Center", "version": { "version_data": [ { "version_affected": "\u003e=", "version_value": "2.0.2" }, { "version_affected": "\u003c", "version_value": "4.5.16" }, { "version_affected": "\u003e=", "version_value": "4.6.0" }, { "version_affected": "\u003c", "version_value": "4.13.8" }, { "version_affected": "\u003e=", "version_value": "4.14.0" }, { "version_affected": "\u003c", "version_value": "4.17.0" } ] } } ] }, "vendor_name": "Atlassian" } ] } }, "data_format": "MITRE", "data_type": "CVE", "data_version": "4.0", "description": { "description_data": [ { "lang": "eng", "value": "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." } ] }, "problemtype": { "problemtype_data": [ { "description": [ { "lang": "eng", "value": "CWE-862: Missing Authorization" } ] } ] }, "references": { "reference_data": [ { "name": "https://jira.atlassian.com/browse/JSDSERVER-8454", "refsource": "MISC", "url": "https://jira.atlassian.com/browse/JSDSERVER-8454" }, { "name": "https://jira.atlassian.com/browse/JRASERVER-72566", "refsource": "MISC", "url": "https://jira.atlassian.com/browse/JRASERVER-72566" }, { "name": "https://confluence.atlassian.com/adminjiraserver/jira-data-center-and-jira-service-management-data-center-security-advisory-2021-07-21-1063571388.html", "refsource": "MISC", "url": "https://confluence.atlassian.com/adminjiraserver/jira-data-center-and-jira-service-management-data-center-security-advisory-2021-07-21-1063571388.html" } ] } }, "nvd.nist.gov": { "configurations": { "CVE_data_version": "4.0", "nodes": [ { "children": [], "cpe_match": [ { "cpe23Uri": "cpe:2.3:a:atlassian:jira_data_center:*:*:*:*:*:*:*:*", "cpe_name": [], "versionEndExcluding": "8.17.0", "versionStartIncluding": "8.14.0", "vulnerable": true }, { "cpe23Uri": "cpe:2.3:a:atlassian:jira_data_center:*:*:*:*:*:*:*:*", "cpe_name": [], "versionEndExcluding": "8.5.16", "versionStartIncluding": "6.3.0", "vulnerable": true }, { "cpe23Uri": "cpe:2.3:a:atlassian:jira_data_center:*:*:*:*:*:*:*:*", "cpe_name": [], "versionEndExcluding": "8.13.8", "versionStartIncluding": "8.6.0", "vulnerable": true }, { "cpe23Uri": "cpe:2.3:a:atlassian:jira_service_desk:*:*:*:*:data_center:*:*:*", "cpe_name": [], "versionEndExcluding": "4.13.8", "versionStartIncluding": "4.6.0", "vulnerable": true }, { "cpe23Uri": "cpe:2.3:a:atlassian:jira_service_management:*:*:*:*:data_center:*:*:*", "cpe_name": [], "versionEndExcluding": "4.17.0", "versionStartIncluding": "4.14.0", "vulnerable": true }, { "cpe23Uri": "cpe:2.3:a:atlassian:jira_service_desk:*:*:*:*:data_center:*:*:*", "cpe_name": [], "versionEndExcluding": "4.5.16", "versionStartIncluding": "2.0.2", "vulnerable": true } ], "operator": "OR" } ] }, "cve": { "CVE_data_meta": { "ASSIGNER": "security@atlassian.com", "ID": "CVE-2020-36239" }, "data_format": "MITRE", "data_type": "CVE", "data_version": "4.0", "description": { "description_data": [ { "lang": "en", "value": "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." } ] }, "problemtype": { "problemtype_data": [ { "description": [ { "lang": "en", "value": "CWE-306" } ] } ] }, "references": { "reference_data": [ { "name": "https://jira.atlassian.com/browse/JRASERVER-72566", "refsource": "MISC", "tags": [ "Issue Tracking", "Vendor Advisory" ], "url": "https://jira.atlassian.com/browse/JRASERVER-72566" }, { "name": "https://confluence.atlassian.com/adminjiraserver/jira-data-center-and-jira-service-management-data-center-security-advisory-2021-07-21-1063571388.html", "refsource": "MISC", "tags": [ "Patch", "Vendor Advisory" ], "url": "https://confluence.atlassian.com/adminjiraserver/jira-data-center-and-jira-service-management-data-center-security-advisory-2021-07-21-1063571388.html" }, { "name": "https://jira.atlassian.com/browse/JSDSERVER-8454", "refsource": "MISC", "tags": [ "Issue Tracking", "Vendor Advisory" ], "url": "https://jira.atlassian.com/browse/JSDSERVER-8454" } ] } }, "impact": { "baseMetricV2": { "acInsufInfo": false, "cvssV2": { "accessComplexity": "LOW", "accessVector": "NETWORK", "authentication": "NONE", "availabilityImpact": "PARTIAL", "baseScore": 7.5, "confidentialityImpact": "PARTIAL", "integrityImpact": "PARTIAL", "vectorString": "AV:N/AC:L/Au:N/C:P/I:P/A:P", "version": "2.0" }, "exploitabilityScore": 10.0, "impactScore": 6.4, "obtainAllPrivilege": false, "obtainOtherPrivilege": false, "obtainUserPrivilege": false, "severity": "HIGH", "userInteractionRequired": false }, "baseMetricV3": { "cvssV3": { "attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "baseScore": 9.8, "baseSeverity": "CRITICAL", "confidentialityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "version": "3.1" }, "exploitabilityScore": 3.9, "impactScore": 5.9 } }, "lastModifiedDate": "2022-08-01T16:32Z", "publishedDate": "2021-07-29T11:15Z" } } }
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.