Page 4 of 19 results (0.004 seconds)

CVSS: 4.9EPSS: 0%CPEs: 1EXPL: 0

Various resources in Atlassian Crowd before version 2.10.1 allow remote attackers with administration rights to learn the passwords of configured LDAP directories by examining the responses to requests for these resources. Varios recursos en Atlassian Crowd, en versiones anteriores a la 2.10.1, permiten a los atacantes remotos con derechos de administrador averiguar las contraseñas de los directorios LDAP configurados, analizando las respuestas a las peticiones para dichos recursos. • https://jira.atlassian.com/browse/CWD-5060 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •

CVSS: 6.8EPSS: 0%CPEs: 1EXPL: 0

The 'crowd-application' plugin module (notably used by the Google Apps plugin) in Atlassian Crowd from version 1.5.0 before version 3.1.2 allowed an attacker to impersonate a Crowd user in REST requests by being able to authenticate to a directory bound to an application using the feature. Given the following situation: the Crowd application is bound to directory 1 and has a user called admin and the Google Apps application is bound to directory 2, which also has a user called admin, it was possible to authenticate REST requests using the credentials of the user coming from directory 2 and impersonate the user from directory 1. El módulo del plugin "crowd-application" (empleado principalmente por el plugin Google Apps) en Atlassian Crowd, desde la versión 1.5.0 y antes de la versión 3.1.2, permitía que un atacante suplantase a un usuario de Crowd en peticiones REST pudiendo autenticarse en un directorio vinculado a una aplicación que emplee esa característica. En la siguiente situación: la aplicación Crowd está enlazada al directorio 1 y tiene un usuario llamado admin y la aplicación Google Apps está enlazada al directorio 2, que también tiene un usuario llamado admin, era posible autenticar peticiones REST empleando las credenciales del usuario que viene del directorio 2 y suplanta al usuario del directorio 1. • https://jira.atlassian.com/browse/CWD-5009 • CWE-287: Improper Authentication CWE-863: Incorrect Authorization •

CVSS: 9.8EPSS: 1%CPEs: 3EXPL: 0

The LDAP directory connector in Atlassian Crowd before 2.8.8 and 2.9.x before 2.9.5 allows remote attackers to execute arbitrary code via an LDAP attribute with a crafted serialized Java object, aka LDAP entry poisoning. El conector de directorio LDAP en Atlassian Crowd en versiones anteriores a 2.8.8 y 2.9.x en versiones anteriores a 2.9.5 permite a atacantes remotos ejecutar código arbitrario a través de un atributo LDAP con un objeto Java serializado manipulado, también conocido como envenenamiento de entrada LDAP. • http://www.securityfocus.com/archive/1/539655/100/0/threaded http://www.securityfocus.com/bid/93826 https://confluence.atlassian.com/crowd/crowd-security-advisory-2016-10-19-856697283.html https://jira.atlassian.com/browse/CWD-4790 https://www.blackhat.com/docs/us-16/materials/us-16-Munoz-A-Journey-From-JNDI-LDAP-Manipulation-To-RCE-wp.pdf • CWE-20: Improper Input Validation •

CVSS: 7.5EPSS: 1%CPEs: 1EXPL: 1

Atlassian Crowd 2.6.3 allows remote attackers to execute arbitrary commands via unspecified vectors related to a "symmetric backdoor." NOTE: as of 20130704, the vendor could not reproduce the issue, stating "We've been unable to substantiate the existence of [CVE-2013-3926]. The author of the article has not contacted Atlassian and has provided no detail, making it difficult to validate the claim... If we can confirm that there is a vulnerability, a patch will be issued. ** DISPUTADA ** Atlassian Crowd 2.6.3 permite a atacantes remotos ejecutar comandos arbitrarios a través de vectores relacionados con una 'puerta trasera simétrica.' NOTA: desde el 04072013, el proveedor no ha podido reproducir el problema, diciendo que 'No hemos sido capaces de corroborar la existencia del [CVE-2013-3926]. • http://it.slashdot.org/story/13/07/01/0011217/backdoor-discovered-in-atlassian-crowd http://www.commandfive.com/papers/C5_TA_2013_3925_AtlassianCrowd.pdf •