<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 14 Oct 2026 22:11:23 +0000</lastBuildDate>
    <item>
      <title>bdu:2023-01918</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2023-01918</link>
      <description>bdu:2023-01918</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2023-01918</guid>
    </item>
    <item>
      <title>EUVD-2026-218843</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-218843</link>
      <description>EUVD-2026-218843</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-218843</guid>
    </item>
    <item>
      <title>fkie_cve-2023-28115</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-28115</link>
      <description>&lt;p&gt;Snappy is a PHP library allowing thumbnail, snapshot or PDF generation from a url or a html page. Prior to version 1.4.2, Snappy is vulnerable to PHAR deserialization due to a lack of checking on the protocol before passing it into the `file_exists()` function. If an attacker can upload files of any type to the server he can pass in the phar:// protocol to unserialize the uploaded file and instantiate arbitrary PHP objects. This can lead to remote code execution especially when snappy is used with frameworks with documented POP chains like Laravel/Symfony vulnerable developer code. If a user can control the output file from the `generateFromHtml()` function, it will invoke deserialization. This vulnerability is capable of remote code execution if Snappy is used with frameworks or developer code with vulnerable POP chains. It has been fixed in version 1.4.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Snappy is a PHP library allowing thumbnail, snapshot or PDF generation from a url or a html page. Prior to version 1.4.2, Snappy is vulnerable to PHAR deserialization due to a lack of checking on the protocol before passing it into the `file_exists()` function. If an attacker can upload files of any type to the server he can pass in the phar:// protocol to unserialize the uploaded file and instantiate arbitrary PHP objects. This can lead to remote code execution especially when snappy is used with frameworks with documented POP chains like Laravel/Symfony vulnerable developer code. If a user can control the output file from the `generateFromHtml()` function, it will invoke deserialization. This vulnerability is capable of remote code execution if Snappy is used with frameworks or developer code with vulnerable POP chains. It has been fixed in version 1.4.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-28115</guid>
    </item>
    <item>
      <title>GHSA-gq6w-q6wh-jggc — PHAR deserialization allowing remote code execution</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-gq6w-q6wh-jggc</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: knplabs/knp-snappy&lt;/p&gt;
&lt;p&gt;## Description&lt;/p&gt;
&lt;p&gt;snappy is vulnerable to PHAR deserialization due to a lack of checking on the protocol before passing it into the `file_exists()` function. If an attacker can upload files of any type to the server he can pass in the phar:// protocol to unserialize the uploaded file and instantiate arbitrary PHP objects. This can lead to remote code execution especially when snappy is used with frameworks with documented POP chains like Laravel/Symfony vulnerable developer code. If user can control the output file from the `generateFromHtml()` function, it will invoke deserialization.&lt;/p&gt;
&lt;p&gt;## Proof of Concept&lt;/p&gt;
&lt;p&gt;Install Snappy via composer require `knplabs/knp-snappy`. After that, under snappy directory, create an `index.php` file with this vulnerable code.&lt;/p&gt;
&lt;p&gt;```php
&amp;lt;?php
// index.php&lt;/p&gt;
&lt;p&gt;// include autoloader
require __DIR__ . &amp;#39;/vendor/autoload.php&amp;#39;;&lt;/p&gt;
&lt;p&gt;// reference the snappy namespace
use Knp\Snappy\Pdf;&lt;/p&gt;
&lt;p&gt;// vulnerable object
class VulnerableClass {
    public $fileName;
    public $callback;&lt;/p&gt;
&lt;p&gt;function __destruct() {
        call_user_func($this-&amp;gt;callback, $this-&amp;gt;fileName);
    }
}&lt;/p&gt;
&lt;p&gt;$snappy = new Pdf(&amp;#39;/usr/local/bin/wkhtmltopdf&amp;#39;);
// generate pdf from html content and save it at phar://poc.phar
$snappy-&amp;gt;generateFromHtml(&amp;#39;&amp;lt;h1&amp;gt;Bill&amp;lt;/h1&amp;gt;&amp;lt;p&amp;gt;You owe me money, dude.&amp;lt;/p&amp;gt;&amp;#39;, &amp;#39;phar://poc.phar&amp;#39;);
```&lt;/p&gt;
&lt;p&gt;As an attacker, we going to generate the malicious phar using this script.&lt;/p&gt;
&lt;p&gt;```php
&amp;lt;?php
// generate_phar.php&lt;/p&gt;
&lt;p&gt;class VulnerableClass { }
// Create a new instance of the Dummy class and modify i…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: knplabs/knp-snappy&lt;/p&gt;
&lt;p&gt;## Description&lt;/p&gt;
&lt;p&gt;snappy is vulnerable to PHAR deserialization due to a lack of checking on the protocol before passing it into the `file_exists()` function. If an attacker can upload files of any type to the server he can pass in the phar:// protocol to unserialize the uploaded file and instantiate arbitrary PHP objects. This can lead to remote code execution especially when snappy is used with frameworks with documented POP chains like Laravel/Symfony vulnerable developer code. If user can control the output file from the `generateFromHtml()` function, it will invoke deserialization.&lt;/p&gt;
&lt;p&gt;## Proof of Concept&lt;/p&gt;
&lt;p&gt;Install Snappy via composer require `knplabs/knp-snappy`. After that, under snappy directory, create an `index.php` file with this vulnerable code.&lt;/p&gt;
&lt;p&gt;```php
&amp;lt;?php
// index.php&lt;/p&gt;
&lt;p&gt;// include autoloader
require __DIR__ . &amp;#39;/vendor/autoload.php&amp;#39;;&lt;/p&gt;
&lt;p&gt;// reference the snappy namespace
use Knp\Snappy\Pdf;&lt;/p&gt;
&lt;p&gt;// vulnerable object
class VulnerableClass {
    public $fileName;
    public $callback;&lt;/p&gt;
&lt;p&gt;function __destruct() {
        call_user_func($this-&amp;gt;callback, $this-&amp;gt;fileName);
    }
}&lt;/p&gt;
&lt;p&gt;$snappy = new Pdf(&amp;#39;/usr/local/bin/wkhtmltopdf&amp;#39;);
// generate pdf from html content and save it at phar://poc.phar
$snappy-&amp;gt;generateFromHtml(&amp;#39;&amp;lt;h1&amp;gt;Bill&amp;lt;/h1&amp;gt;&amp;lt;p&amp;gt;You owe me money, dude.&amp;lt;/p&amp;gt;&amp;#39;, &amp;#39;phar://poc.phar&amp;#39;);
```&lt;/p&gt;
&lt;p&gt;As an attacker, we going to generate the malicious phar using this script.&lt;/p&gt;
&lt;p&gt;```php
&amp;lt;?php
// generate_phar.php&lt;/p&gt;
&lt;p&gt;class VulnerableClass { }
// Create a new instance of the Dummy class and modify i…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-gq6w-q6wh-jggc</guid>
    </item>
    <item>
      <title>gsd-2023-28115</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-28115</link>
      <description>gsd-2023-28115</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-28115</guid>
    </item>
    <item>
      <title>msrc_CVE-2023-28115 — Snappy vulnerable to PHAR deserialization, allowing remote code execution</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2023-28115</link>
      <description>msrc_CVE-2023-28115</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2023-28115</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-28115</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-28115</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: civicrm, Ubuntu:Pro:18.04:LTS: civicrm, Ubuntu:Pro:20.04:LTS: civicrm, Ubuntu:Pro:22.04:LTS: civicrm&lt;/p&gt;
&lt;p&gt;Snappy is a PHP library allowing thumbnail, snapshot or PDF generation from a url or a html page. Prior to version 1.4.2, Snappy is vulnerable to PHAR deserialization due to a lack of checking on the protocol before passing it into the `file_exists()` function. If an attacker can upload files of any type to the server he can pass in the phar:// protocol to unserialize the uploaded file and instantiate arbitrary PHP objects. This can lead to remote code execution especially when snappy is used with frameworks with documented POP chains like Laravel/Symfony vulnerable developer code. If a user can control the output file from the `generateFromHtml()` function, it will invoke deserialization. This vulnerability is capable of remote code execution if Snappy is used with frameworks or developer code with vulnerable POP chains. It has been fixed in version 1.4.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: civicrm, Ubuntu:Pro:18.04:LTS: civicrm, Ubuntu:Pro:20.04:LTS: civicrm, Ubuntu:Pro:22.04:LTS: civicrm&lt;/p&gt;
&lt;p&gt;Snappy is a PHP library allowing thumbnail, snapshot or PDF generation from a url or a html page. Prior to version 1.4.2, Snappy is vulnerable to PHAR deserialization due to a lack of checking on the protocol before passing it into the `file_exists()` function. If an attacker can upload files of any type to the server he can pass in the phar:// protocol to unserialize the uploaded file and instantiate arbitrary PHP objects. This can lead to remote code execution especially when snappy is used with frameworks with documented POP chains like Laravel/Symfony vulnerable developer code. If a user can control the output file from the `generateFromHtml()` function, it will invoke deserialization. This vulnerability is capable of remote code execution if Snappy is used with frameworks or developer code with vulnerable POP chains. It has been fixed in version 1.4.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-28115</guid>
    </item>
  </channel>
</rss>
