<?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>Sat, 10 Oct 2026 17:33:00 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-4546</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-4546</link>
      <description>EUVD-2026-4546</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-4546</guid>
    </item>
    <item>
      <title>fkie_cve-2024-28864</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-28864</link>
      <description>&lt;p&gt;SecureProps is a PHP library designed to simplify the encryption and decryption of property data in objects. A vulnerability in SecureProps version 1.2.0 and 1.2.1 involves a regex failing to detect tags during decryption of encrypted data. This occurs when the encrypted data has been encoded with `NullEncoder` and passed to `TagAwareCipher`, and contains special characters such as `\n`. As a result, the decryption process is skipped since the tags are not detected. This causes the encrypted data to be returned in plain format.  The vulnerability affects users who implement `TagAwareCipher` with any base cipher that has `NullEncoder` (not default). The patch for the issue has been released. Users are advised to update to version 1.2.2. As a workaround, one may use the default `Base64Encoder` with the base cipher decorated with `TagAwareCipher` to prevent special characters in the encrypted string from interfering with regex tag detection logic.  This workaround is safe but may involve double encoding since `TagAwareCipher` uses `NullEncoder` by default.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;SecureProps is a PHP library designed to simplify the encryption and decryption of property data in objects. A vulnerability in SecureProps version 1.2.0 and 1.2.1 involves a regex failing to detect tags during decryption of encrypted data. This occurs when the encrypted data has been encoded with `NullEncoder` and passed to `TagAwareCipher`, and contains special characters such as `\n`. As a result, the decryption process is skipped since the tags are not detected. This causes the encrypted data to be returned in plain format.  The vulnerability affects users who implement `TagAwareCipher` with any base cipher that has `NullEncoder` (not default). The patch for the issue has been released. Users are advised to update to version 1.2.2. As a workaround, one may use the default `Base64Encoder` with the base cipher decorated with `TagAwareCipher` to prevent special characters in the encrypted string from interfering with regex tag detection logic.  This workaround is safe but may involve double encoding since `TagAwareCipher` uses `NullEncoder` by default.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-28864</guid>
    </item>
    <item>
      <title>GHSA-rj29-j2g4-77q8 — [TagAwareCipher] - Decryption Failure (Regex Match)</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-rj29-j2g4-77q8</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: ilicmiljan/secure-props&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Vulnerability in **SecureProps** involves a regex failing to detect tags during decryption of encrypted data.&lt;/p&gt;
&lt;p&gt;This occurs when the encrypted data has been encoded with `NullEncoder` and passed to `TagAwareCipher`, and contains special characters such as `\n`. As a result, the decryption process is skipped since the tags are not detected. This causes the encrypted data to be returned in plain format.&lt;/p&gt;
&lt;p&gt;The vulnerability affects users who implement `TagAwareCipher` with any base cipher that has `NullEncoder` (not default).&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The patch for the issue has been released. Users are advised to update to version **1.2.2**.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;**The main recommendation is to update to the latest version as there are no breaking changes.**&lt;/p&gt;
&lt;p&gt;If that&amp;#39;s not possible, you can use the default `Base64Encoder` with the base cipher decorated with `TagAwareCipher` to prevent special characters in the encrypted string from interfering with regex tag detection logic.&lt;/p&gt;
&lt;p&gt;This workaround is safe but may involve double encoding since `TagAwareCipher` uses `Base64Encoder` by default.
 
### References&lt;/p&gt;
&lt;p&gt;Reported issue: https://github.com/IlicMiljan/Secure-Props/issues/20
Pull request resolving bug: https://github.com/IlicMiljan/Secure-Props/pull/21&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: ilicmiljan/secure-props&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Vulnerability in **SecureProps** involves a regex failing to detect tags during decryption of encrypted data.&lt;/p&gt;
&lt;p&gt;This occurs when the encrypted data has been encoded with `NullEncoder` and passed to `TagAwareCipher`, and contains special characters such as `\n`. As a result, the decryption process is skipped since the tags are not detected. This causes the encrypted data to be returned in plain format.&lt;/p&gt;
&lt;p&gt;The vulnerability affects users who implement `TagAwareCipher` with any base cipher that has `NullEncoder` (not default).&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The patch for the issue has been released. Users are advised to update to version **1.2.2**.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;**The main recommendation is to update to the latest version as there are no breaking changes.**&lt;/p&gt;
&lt;p&gt;If that&amp;#39;s not possible, you can use the default `Base64Encoder` with the base cipher decorated with `TagAwareCipher` to prevent special characters in the encrypted string from interfering with regex tag detection logic.&lt;/p&gt;
&lt;p&gt;This workaround is safe but may involve double encoding since `TagAwareCipher` uses `Base64Encoder` by default.
 
### References&lt;/p&gt;
&lt;p&gt;Reported issue: https://github.com/IlicMiljan/Secure-Props/issues/20
Pull request resolving bug: https://github.com/IlicMiljan/Secure-Props/pull/21&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-rj29-j2g4-77q8</guid>
    </item>
    <item>
      <title>gsd-2024-28864</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-28864</link>
      <description>gsd-2024-28864</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-28864</guid>
    </item>
  </channel>
</rss>
