CVSS: 5.9EPSS: 0%CPEs: 1EXPL: 0CVE-2017-6921 – File REST resource does not properly validate
https://notcve.org/view.php?id=CVE-2017-6921
In Drupal 8 prior to 8.3.4; The file REST resource does not properly validate some fields when manipulating files. A site is only affected by this if the site has the RESTful Web Services (rest) module enabled, the file REST resource is enabled and allows PATCH requests, and an attacker can get or register a user account on the site with permissions to upload files and to modify the file resource. En Drupal 8, en versiones anteriores a la 8.3.4, el recurso de archivo REST no valida correctamente algunos campos al manipular archivos. Un sitio solo se ve afectado por esto si tiene el módulo RESTful Web Services (rest) habilitado, el recurso de archivo REST habilitado, permite peticiones PATCH, y un atacante es capaz de obtener o registrar una cuenta de usuario en el sitio con permisos para subir archivos y modificar el recurso de archivo. • http://www.securityfocus.com/bid/99222 http://www.securitytracker.com/id/1038781 https://www.drupal.org/forum/newsletters/security-advisories-for-drupal-core/2017-06-21/drupal-core-multiple • CWE-20: Improper Input Validation •
CVSS: 7.4EPSS: 0%CPEs: 1EXPL: 0CVE-2017-6924 – REST API can bypass comment approval - Access Bypass - Moderately Critical
https://notcve.org/view.php?id=CVE-2017-6924
In Drupal 8 prior to 8.3.7; When using the REST API, users without the correct permission can post comments via REST that are approved even if the user does not have permission to post approved comments. This issue only affects sites that have the RESTful Web Services (rest) module enabled, the comment entity REST resource enabled, and where an attacker can access a user account on the site with permissions to post comments, or where anonymous users can post comments. Al emplear la API REST en Drupal 8, en versiones anteriores a la 8.3.4, los usuarios que carezcan del permiso correcto pueden publicar comentarios mediante REST que están aprobados incluso aunque dicho usuario no tenga permiso para publicar comentarios aprobados. Este problema solo afecta a sitios que tengan el módulo RESTful Web Services (rest) habilitado, el recurso REST de comentario habilitado y si un atacante puede acceder a una cuenta de usuario en el sitio con permisos para publicar comentarios (o donde los usuarios anónimos puedan publicar comentarios). • http://www.securityfocus.com/bid/100368 http://www.securitytracker.com/id/1039200 https://www.drupal.org/forum/newsletters/security-advisories-for-drupal-core/2017-08-16/drupal-core-multiple • CWE-269: Improper Privilege Management •
CVSS: 9.8EPSS: 0%CPEs: 1EXPL: 0CVE-2017-6925
https://notcve.org/view.php?id=CVE-2017-6925
In versions of Drupal 8 core prior to 8.3.7; There is a vulnerability in the entity access system that could allow unwanted access to view, create, update, or delete entities. This only affects entities that do not use or do not have UUIDs, and entities that have different access restrictions on different revisions of the same entity. En versiones de Drupal 8 core anteriores a la 8.3.7, hay una vulnerabilidad en el sistema de acceso de entidades que podría permitir el acceso no deseado para visualizar, crear, actualizar o eliminar entidades. Esto solo afecta a las entidades que no emplean o no poseen UUID, así como a las entidades que tienen diferentes restricciones de acceso en diferentes revisiones de la misma entidad. • http://www.securityfocus.com/bid/100368 http://www.securitytracker.com/id/1039200 https://www.drupal.org/forum/newsletters/security-advisories-for-drupal-core/2017-08-16/drupal-core-multiple •
CVSS: 9.8EPSS: 6%CPEs: 1EXPL: 0CVE-2017-6920
https://notcve.org/view.php?id=CVE-2017-6920
Drupal core 8 before versions 8.3.4 allows remote attackers to execute arbitrary code due to the PECL YAML parser not handling PHP objects safely during certain operations. Drupal core 8 en versiones anteriores a la 8.3.4 permite que los atacantes remotos ejecuten código arbitrario debido a que el analizador PECL YAML no maneja objetos PHP de forma segura durante determinadas operaciones. • http://www.securityfocus.com/bid/99211 http://www.securitytracker.com/id/1038781 https://www.drupal.org/forum/newsletters/security-advisories-for-drupal-core/2017-06-21/drupal-core-multiple • CWE-19: Data Processing Errors •
CVSS: 6.5EPSS: 87%CPEs: 9EXPL: 0CVE-2018-14773
https://notcve.org/view.php?id=CVE-2018-14773
An issue was discovered in Http Foundation in Symfony 2.7.0 through 2.7.48, 2.8.0 through 2.8.43, 3.3.0 through 3.3.17, 3.4.0 through 3.4.13, 4.0.0 through 4.0.13, and 4.1.0 through 4.1.2. It arises from support for a (legacy) IIS header that lets users override the path in the request URL via the X-Original-URL or X-Rewrite-URL HTTP request header. These headers are designed for IIS support, but it's not verified that the server is in fact running IIS, which means anybody who can send these requests to an application can trigger this. This affects \Symfony\Component\HttpFoundation\Request::prepareRequestUri() where X-Original-URL and X_REWRITE_URL are both used. The fix drops support for these methods so that they cannot be used as attack vectors such as web cache poisoning. • http://www.securityfocus.com/bid/104943 http://www.securitytracker.com/id/1041405 https://github.com/symfony/symfony/commit/e447e8b92148ddb3d1956b96638600ec95e08f6b https://lists.debian.org/debian-lts-announce/2019/03/msg00009.html https://seclists.org/bugtraq/2019/May/21 https://symfony.com/blog/cve-2018-14773-remove-support-for-legacy-and-risky-http-headers https://www.debian.org/security/2019/dsa-4441 https://www.drupal.org/SA-CORE-2018-005 •