https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 08:53:22 +0000 https://cve.radiocsirt.org/vuln/bdu:2020-00063 bdu:2020-00063 https://cve.radiocsirt.org/vuln/bdu:2020-00063 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0419 certfr-2024-avi-0419 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0419 https://cve.radiocsirt.org/vuln/cnvd-2018-25795 cnvd-2018-25795 https://cve.radiocsirt.org/vuln/cnvd-2018-25795 https://cve.radiocsirt.org/vuln/euvd-2026-68569 EUVD-2026-68569 https://cve.radiocsirt.org/vuln/euvd-2026-68569 https://cve.radiocsirt.org/vuln/fkie_cve-2018-17190 <p>In all versions of Apache Spark, its standalone resource manager accepts code to execute on a &#39;master&#39; host, that then runs that code on &#39;worker&#39; hosts. The master itself does not, by design, execute user code. A specially-crafted request to the master can, however, cause the master to execute code too. Note that this does not affect standalone clusters with authentication enabled. While the master host typically has less outbound access to other resources than a worker, the execution of code on the master is nevertheless unexpected.</p> <p>In all versions of Apache Spark, its standalone resource manager accepts code to execute on a &#39;master&#39; host, that then runs that code on &#39;worker&#39; hosts. The master itself does not, by design, execute user code. A specially-crafted request to the master can, however, cause the master to execute code too. Note that this does not affect standalone clusters with authentication enabled. While the master host typically has less outbound access to other resources than a worker, the execution of code on the master is nevertheless unexpected.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2018-17190 https://cve.radiocsirt.org/vuln/ghsa-phg2-9c5g-m4q7 <p><strong>Affected:</strong> Maven: org.apache.spark:spark-core_2.11, Maven: org.apache.spark:spark-core_2.10</p> <p>In all versions of Apache Spark, its standalone resource manager accepts code to execute on a &#39;master&#39; host, that then runs that code on &#39;worker&#39; hosts. The master itself does not, by design, execute user code. A specially-crafted request to the master can, however, cause the master to execute code too. Note that this does not affect standalone clusters with authentication enabled. While the master host typically has less outbound access to other resources than a worker, the execution of code on the master is nevertheless unexpected.</p> <p># Mitigation Enable authentication on any Spark standalone cluster that is not otherwise secured from unwanted access, for example by network-level restrictions. Use spark.authenticate and related security properties described at https://spark.apache.org/docs/latest/security.html</p> <p><strong>Affected:</strong> Maven: org.apache.spark:spark-core_2.11, Maven: org.apache.spark:spark-core_2.10</p> <p>In all versions of Apache Spark, its standalone resource manager accepts code to execute on a &#39;master&#39; host, that then runs that code on &#39;worker&#39; hosts. The master itself does not, by design, execute user code. A specially-crafted request to the master can, however, cause the master to execute code too. Note that this does not affect standalone clusters with authentication enabled. While the master host typically has less outbound access to other resources than a worker, the execution of code on the master is nevertheless unexpected.</p> <p># Mitigation Enable authentication on any Spark standalone cluster that is not otherwise secured from unwanted access, for example by network-level restrictions. Use spark.authenticate and related security properties described at https://spark.apache.org/docs/latest/security.html</p> https://cve.radiocsirt.org/vuln/ghsa-phg2-9c5g-m4q7 https://cve.radiocsirt.org/vuln/gsd-2018-17190 gsd-2018-17190 https://cve.radiocsirt.org/vuln/gsd-2018-17190