CVSS: 5.7EPSS: 0%CPEs: 6EXPL: 0CVE-2021-43959
https://notcve.org/view.php?id=CVE-2021-43959
Affected versions of Atlassian Jira Service Management Server and Data Center allow authenticated remote attackers to access the content of internal network resources via a Server-Side Request Forgery (SSRF) vulnerability in the CSV importing feature of JSM Insight. When running in an environment like Amazon EC2, this flaw may be used to access to a metadata resource that provides access credentials and other potentially confidential information. The affected versions are before version 4.13.20, from version 4.14.0 before 4.20.8, and from version 4.21.0 before 4.22.2. Las versiones afectadas de Atlassian Jira Service Management Server y Data Center permiten a atacantes remotos autenticados acceder al contenido de los recursos de la red interna por medio de una vulnerabilidad de tipo Server-Side Request Forgery (SSRF) en la funcionalidad CSV importing de JSM Insight. Cuando se ejecuta en un entorno como Amazon EC2, este fallo puede usarse para acceder a un recurso de metadatos que proporciona credenciales de acceso y otra información potencialmente confidencial. • https://jira.atlassian.com/browse/JSDSERVER-11898 • CWE-918: Server-Side Request Forgery (SSRF) •
CVSS: 8.8EPSS: 0%CPEs: 42EXPL: 0CVE-2022-26137
https://notcve.org/view.php?id=CVE-2022-26137
A vulnerability in multiple Atlassian products allows a remote, unauthenticated attacker to cause additional Servlet Filters to be invoked when the application processes requests or responses. Atlassian has confirmed and fixed the only known security issue associated with this vulnerability: Cross-origin resource sharing (CORS) bypass. Sending a specially crafted HTTP request can invoke the Servlet Filter used to respond to CORS requests, resulting in a CORS bypass. An attacker that can trick a user into requesting a malicious URL can access the vulnerable application with the victim’s permissions. Atlassian Bamboo versions are affected before 8.0.9, from 8.1.0 before 8.1.8, and from 8.2.0 before 8.2.4. • https://jira.atlassian.com/browse/BAM-21795 https://jira.atlassian.com/browse/BSERV-13370 https://jira.atlassian.com/browse/CONFSERVER-79476 https://jira.atlassian.com/browse/CRUC-8541 https://jira.atlassian.com/browse/CWD-5815 https://jira.atlassian.com/browse/FE-7410 https://jira.atlassian.com/browse/JRASERVER-73897 https://jira.atlassian.com/browse/JSDSERVER-11863 • CWE-180: Incorrect Behavior Order: Validate Before Canonicalize CWE-346: Origin Validation Error •
CVSS: 9.8EPSS: 0%CPEs: 42EXPL: 0CVE-2022-26136
https://notcve.org/view.php?id=CVE-2022-26136
A vulnerability in multiple Atlassian products allows a remote, unauthenticated attacker to bypass Servlet Filters used by first and third party apps. The impact depends on which filters are used by each app, and how the filters are used. This vulnerability can result in authentication bypass and cross-site scripting. Atlassian has released updates that fix the root cause of this vulnerability, but has not exhaustively enumerated all potential consequences of this vulnerability. Atlassian Bamboo versions are affected before 8.0.9, from 8.1.0 before 8.1.8, and from 8.2.0 before 8.2.4. • https://jira.atlassian.com/browse/BAM-21795 https://jira.atlassian.com/browse/BSERV-13370 https://jira.atlassian.com/browse/CONFSERVER-79476 https://jira.atlassian.com/browse/CRUC-8541 https://jira.atlassian.com/browse/CWD-5815 https://jira.atlassian.com/browse/FE-7410 https://jira.atlassian.com/browse/JRASERVER-73897 https://jira.atlassian.com/browse/JSDSERVER-11863 • CWE-180: Incorrect Behavior Order: Validate Before Canonicalize CWE-287: Improper Authentication •
CVSS: 9.0EPSS: 0%CPEs: 4EXPL: 1CVE-2021-39115
https://notcve.org/view.php?id=CVE-2021-39115
Affected versions of Atlassian Jira Service Management Server and Data Center allow remote attackers with "Jira Administrators" access to execute arbitrary Java code or run arbitrary system commands via a Server_Side Template Injection vulnerability in the Email Template feature. The affected versions are before version 4.13.9, and from version 4.14.0 before 4.18.0. Las versiones afectadas de Atlassian Jira Service Management Server y Data Center permiten a atacantes remotos con acceso "Jira Administrators" ejecutar código Java arbitrario o ejecutar comandos del sistema arbitrarios por medio de una vulnerabilidad de Server_Side Template Injection en la funcionalidad Email Template. Las versiones afectadas son anteriores a versión 4.13.9, y desde versión 4.14.0 hasta 4.18.0 • https://github.com/PetrusViet/CVE-2021-39115 https://jira.atlassian.com/browse/JSDSERVER-8665 • CWE-94: Improper Control of Generation of Code ('Code Injection') CWE-96: Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection') •
CVSS: 9.8EPSS: 1%CPEs: 6EXPL: 0CVE-2020-36239
https://notcve.org/view.php?id=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 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. Jira Data Center, Jira Core Data Center, Jira Software Data Center desde la versión 6.3.0 antes de la versión 8.5.16, desde la versión 8.6.0 antes de la versión 8.13.8, desde la 8.14.0 antes de la versión 8.17.0 y Jira Service Management Data Center desde la versión 2.0.2 antes de la versión 4.5.16, desde la versión 4.6.0 antes de la versión 4.13.8, y desde la versión 4.14.0 antes de la versión 4.17.0 expusieron un servicio de red Ehcache RMI que los atacantes, que pueden conectarse al servicio, en el puerto 40001 y potencialmente 40011[0][1], podrían ejecutar código arbitrario de su elección en Jira a través de la deserialización debido a una vulnerabilidad de falta de autenticación. Aunque Atlassian sugiere encarecidamente que se restrinja el acceso a los puertos Ehcache sólo a las instancias del Centro de Datos, las versiones fijas de Jira requerirán ahora un secreto compartido para permitir el acceso al servicio Ehcache. [0] En las versiones de Jira Data Center, Jira Core Data Center y Jira Software Data Center anteriores a la versión 7.13.1, el puerto del objeto Ehcache puede ser asignado aleatoriamente. [1] En las versiones de Jira Service Management Data Center anteriores a la versión 3.16.1, el puerto del objeto Ehcache puede asignarse aleatoriamente • https://confluence.atlassian.com/adminjiraserver/jira-data-center-and-jira-service-management-data-center-security-advisory-2021-07-21-1063571388.html https://jira.atlassian.com/browse/JRASERVER-72566 https://jira.atlassian.com/browse/JSDSERVER-8454 • CWE-306: Missing Authentication for Critical Function CWE-862: Missing Authorization •