CVSS: 4.0EPSS: 0%CPEs: 33EXPL: 1CVE-2021-28163 – jetty: Symlink directory exposes webapp directory contents
https://notcve.org/view.php?id=CVE-2021-28163
01 Apr 2021 — In Eclipse Jetty 9.4.32 to 9.4.38, 10.0.0.beta2 to 10.0.1, and 11.0.0.beta2 to 11.0.1, if a user uses a webapps directory that is a symlink, the contents of the webapps directory is deployed as a static webapp, inadvertently serving the webapps themselves and anything else that might be in that directory. En Eclipse Jetty versiones 9.4.32 hasta 9.4.38, versiones 10.0.0.beta2 hasta 10.0.1 y versiones 11.0.0.beta2 hasta 11.0.1, si un usuario usa un directorio de aplicaciones web que es un enlace simbólico, el... • https://github.com/eclipse/jetty.project/security/advisories/GHSA-j6qj-j888-vvgq • CWE-59: Improper Link Resolution Before File Access ('Link Following') CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •
CVSS: 9.1EPSS: 1%CPEs: 1EXPL: 0CVE-2020-1963
https://notcve.org/view.php?id=CVE-2020-1963
03 Jun 2020 — Apache Ignite uses H2 database to build SQL distributed execution engine. H2 provides SQL functions which could be used by attacker to access to a filesystem. Apache Ignite utiliza la base de datos H2 para construir el motor de ejecución distribuida de SQL. H2 proporciona funciones SQL que el atacante podría usar para acceder a un sistema de archivos. • http://www.openwall.com/lists/oss-security/2020/06/03/2 • CWE-862: Missing Authorization •
CVSS: 9.8EPSS: 6%CPEs: 2EXPL: 0CVE-2018-8018 – ignite: Improper deserialization allows for code execution via GridClientJdkMarshaller endpoint
https://notcve.org/view.php?id=CVE-2018-8018
19 Jul 2018 — In Apache Ignite before 2.4.8 and 2.5.x before 2.5.3, the serialization mechanism does not have a list of classes allowed for serialization/deserialization, which makes it possible to run arbitrary code when 3-rd party vulnerable classes are present in Ignite classpath. The vulnerability can be exploited if the one sends a specially prepared form of a serialized object to GridClientJdkMarshaller deserialization endpoint. En Apache Ignite versión anterior a 2.4.8 y versión 2.5. x versión anterior a 2.5.3, el... • http://www.securityfocus.com/bid/104911 • CWE-502: Deserialization of Untrusted Data •
CVSS: 9.8EPSS: 96%CPEs: 8EXPL: 5CVE-2018-1273 – VMware Tanzu Spring Data Commons Property Binder Vulnerability
https://notcve.org/view.php?id=CVE-2018-1273
11 Apr 2018 — Spring Data Commons, versions prior to 1.13 to 1.13.10, 2.0 to 2.0.5, and older unsupported versions, contain a property binder vulnerability caused by improper neutralization of special elements. An unauthenticated remote malicious user (or attacker) can supply specially crafted request parameters against Spring Data REST backed HTTP resources or using Spring Data's projection-based request payload binding hat can lead to a remote code execution attack. Spring Data Commons, en versiones anteriores a las co... • https://github.com/knqyf263/CVE-2018-1273 • CWE-20: Improper Input Validation CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') CWE-94: Improper Control of Generation of Code ('Code Injection') •
CVSS: 9.8EPSS: 5%CPEs: 1EXPL: 0CVE-2018-1295 – ignite: Possible Execution of Arbitrary Code Within Deserialization Endpoints
https://notcve.org/view.php?id=CVE-2018-1295
02 Apr 2018 — In Apache Ignite 2.3 or earlier, the serialization mechanism does not have a list of classes allowed for serialization/deserialization, which makes it possible to run arbitrary code when 3-rd party vulnerable classes are present in Ignite classpath. The vulnerability can be exploited if the one sends a specially prepared form of a serialized object to one of the deserialization endpoints of some Ignite components - discovery SPI, Ignite persistence, Memcached endpoint, socket steamer. En Apache Ignite 2.3 o... • http://www.securityfocus.com/bid/103692 • CWE-502: Deserialization of Untrusted Data •
CVSS: 7.5EPSS: 0%CPEs: 13EXPL: 0CVE-2017-7686
https://notcve.org/view.php?id=CVE-2017-7686
28 Jun 2017 — Apache Ignite 1.0.0-RC3 to 2.0 uses an update notifier component to update the users about new project releases that include additional functionality, bug fixes and performance improvements. To do that the component communicates to an external PHP server (http://ignite.run) where it needs to send some system properties like Apache Ignite or Java version. Some of the properties might contain user sensitive information. Apache Ignite 1.0.0-RC3 a 2.0 emplea un componente de notificación de actualizaciones para... • http://apache-ignite-developers.2346864.n4.nabble.com/CVE-2017-7686-Apache-Ignite-Information-Disclosure-td19168.html • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •
CVSS: 5.9EPSS: 0%CPEs: 1EXPL: 0CVE-2016-6805 – Apache Ignite 1.8 XXE Injection
https://notcve.org/view.php?id=CVE-2016-6805
07 Apr 2017 — Apache Ignite before 1.9 allows man-in-the-middle attackers to read arbitrary files via XXE in modified update-notifier documents. Apache Ignite en versiones anteriores a 1.9 permite a los atacantes del tipo man-in-the-middle leer archivos arbitrarios a través de XXE en documentos modificados de notificación de actualización. Apache Ignite versions 1.0.0-RC3 through 1.8 suffer from an arbitrary file read that can be leveraged due to an eXternal Xml Entity vulnerability. • http://seclists.org/oss-sec/2017/q2/31 • CWE-611: Improper Restriction of XML External Entity Reference •