CVSS: 6.5EPSS: 0%CPEs: 2EXPL: 0CVE-2020-7019
https://notcve.org/view.php?id=CVE-2020-7019
18 Aug 2020 — In Elasticsearch before 7.9.0 and 6.8.12 a field disclosure flaw was found when running a scrolling search with Field Level Security. If a user runs the same query another more privileged user recently ran, the scrolling search can leak fields that should be hidden. This could result in an attacker gaining additional permissions against a restricted index. En Elasticsearch versiones anteriores a 7.9.0 y 6.8.12, se encontró un fallo de divulgación de campo al ejecutar una búsqueda de desplazamiento con Field... • https://discuss.elastic.co/t/elastic-stack-7-9-0-and-6-8-12-security-update/245456 • CWE-269: Improper Privilege Management CWE-270: Privilege Context Switching Error •
CVSS: 8.8EPSS: 0%CPEs: 2EXPL: 0CVE-2020-7014
https://notcve.org/view.php?id=CVE-2020-7014
03 Jun 2020 — The fix for CVE-2020-7009 was found to be incomplete. Elasticsearch versions from 6.7.0 to 6.8.7 and 7.0.0 to 7.6.1 contain a privilege escalation flaw if an attacker is able to create API keys and also authentication tokens. An attacker who is able to generate an API key and an authentication token can perform a series of steps that result in an authentication token being generated with elevated privileges. Se encontró que la solución para CVE-2020-7009 estaba incompleta. Elasticsearch versiones desde 6.7.... • https://security.netapp.com/advisory/ntap-20200619-0003 • CWE-266: Incorrect Privilege Assignment CWE-269: Improper Privilege Management •
CVSS: 8.8EPSS: 0%CPEs: 2EXPL: 0CVE-2020-7009
https://notcve.org/view.php?id=CVE-2020-7009
31 Mar 2020 — Elasticsearch versions from 6.7.0 before 6.8.8 and 7.0.0 before 7.6.2 contain a privilege escalation flaw if an attacker is able to create API keys. An attacker who is able to generate an API key can perform a series of steps that result in an API key being generated with elevated privileges. Elasticsearch versiones desde 6.7.0 en versiones anteriores a la 6.8.8 y versiones 7.0.0 en versiones anteriores a la 7.6.2 contienen un fallo de escalada de privilegios si un atacante es capaz de crear claves de la AP... • https://discuss.elastic.co/t/elastic-stack-6-8-8-and-7-6-2-security-update/225920 • CWE-266: Incorrect Privilege Assignment CWE-269: Improper Privilege Management •
CVSS: 5.3EPSS: 0%CPEs: 2EXPL: 0CVE-2019-7619
https://notcve.org/view.php?id=CVE-2019-7619
30 Oct 2019 — Elasticsearch versions 7.0.0-7.3.2 and 6.7.0-6.8.3 contain a username disclosure flaw was found in the API Key service. An unauthenticated attacker could send a specially crafted request and determine if a username exists in the Elasticsearch native realm. Elasticsearch versiones 7.0.0 hasta 7.3.2 y versiones 6.7.0 hasta 6.8.3, contienen un fallo de divulgación de nombre de usuario que se encontró en el servicio Key de la API. Un atacante no autenticado podría enviar una petición especialmente diseñada y de... • https://discuss.elastic.co/t/elastic-stack-6-8-4-security-update/204908 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •
CVSS: 7.8EPSS: 0%CPEs: 60EXPL: 0CVE-2019-3800 – CF CLI writes the client id and secret to config file
https://notcve.org/view.php?id=CVE-2019-3800
05 Aug 2019 — CF CLI version prior to v6.45.0 (bosh release version 1.16.0) writes the client id and secret to its config file when the user authenticates with --client-credentials flag. A local authenticated malicious user with access to the CF CLI config file can act as that client, who is the owner of the leaked credentials. La CLI de CF anterior a versión v6.45.0 (versión de lanzamiento bosh 1.16.0), escribe el id y el secreto del cliente hacia su archivo de configuración cuando el usuario se autentica con el flag --... • https://pivotal.io/security/cve-2019-3800 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor CWE-522: Insufficiently Protected Credentials •
CVSS: 5.9EPSS: 0%CPEs: 2EXPL: 0CVE-2019-7614
https://notcve.org/view.php?id=CVE-2019-7614
30 Jul 2019 — A race condition flaw was found in the response headers Elasticsearch versions before 7.2.1 and 6.8.2 returns to a request. On a system with multiple users submitting requests, it could be possible for an attacker to gain access to response header containing sensitive data from another user. Se detectó un fallo de condición de carrera en los encabezados de respuesta que devuelve una petición de Elasticsearch versiones anteriores a 7.2.1 y 6.8.2. Sobre un sistema con múltiples usuarios que envían peticiones,... • https://www.elastic.co/community/security • CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') •
CVSS: 8.1EPSS: 0%CPEs: 2EXPL: 0CVE-2019-7611 – elasticsearch: Improper permission issue when attaching a new name to an index
https://notcve.org/view.php?id=CVE-2019-7611
25 Mar 2019 — A permission issue was found in Elasticsearch versions before 5.6.15 and 6.6.1 when Field Level Security and Document Level Security are disabled and the _aliases, _shrink, or _split endpoints are used . If the elasticsearch.yml file has xpack.security.dls_fls.enabled set to false, certain permission checks are skipped when users perform one of the actions mentioned above, to make existing data available under a new index/alias name. This could result in an attacker gaining additional permissions against a ... • https://discuss.elastic.co/t/elastic-stack-6-6-1-and-5-6-15-security-update/169077 • CWE-284: Improper Access Control CWE-285: Improper Authorization •
CVSS: 6.5EPSS: 0%CPEs: 1EXPL: 0CVE-2018-17244
https://notcve.org/view.php?id=CVE-2018-17244
20 Dec 2018 — Elasticsearch Security versions 6.4.0 to 6.4.2 contain an error in the way request headers are applied to requests when using the Active Directory, LDAP, Native, or File realms. A request may receive headers intended for another request if the same username is being authenticated concurrently; when used with run as, this can result in the request running as the incorrect user. This could allow a user to access information that they should not have access to. Elasticsearch Security, de la versión 6.4.0 a la ... • http://www.securityfocus.com/bid/106318 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') •
CVSS: 5.9EPSS: 0%CPEs: 2EXPL: 0CVE-2018-17247
https://notcve.org/view.php?id=CVE-2018-17247
20 Dec 2018 — Elasticsearch Security versions 6.5.0 and 6.5.1 contain an XXE flaw in Machine Learning's find_file_structure API. If a policy allowing external network access has been added to Elasticsearch's Java Security Manager then an attacker could send a specially crafted request capable of leaking content of local files on the Elasticsearch node. This could allow a user to access information that they should not have access to. Elasticsearch Security, en versiones 6.5.0 y 6.5.1, contiene un error de XEE (XML Extern... • http://www.securityfocus.com/bid/106294 • CWE-611: Improper Restriction of XML External Entity Reference •
CVSS: 6.5EPSS: 0%CPEs: 2EXPL: 0CVE-2018-3826
https://notcve.org/view.php?id=CVE-2018-3826
19 Sep 2018 — In Elasticsearch versions 6.0.0-beta1 to 6.2.4 a disclosure flaw was found in the _snapshot API. When the access_key and security_key parameters are set using the _snapshot API they can be exposed as plain text by users able to query the _snapshot API. En Elasticsearch desde la versión 6.0.0-beta1 hasta la 6.2.4, se ha detectado una vulnerabilidad de divulgación en la API _snapshot. Cuando los parámetros access_key y security_key están configurados usando la API _snapshot, se pueden exponen como texto plano... • https://discuss.elastic.co/t/elastic-stack-6-3-0-and-5-6-10-security-update/135777 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor CWE-311: Missing Encryption of Sensitive Data •