<?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 07:51:34 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-13470 — RNP 0.18.0 Vulnerable PKESK session keys</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-13470</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ribose RNP&lt;/p&gt;
&lt;p&gt;In RNP version 0.18.0 a refactoring regression causes the symmetric 
session key used for Public-Key Encrypted Session Key (PKESK) packets to
 be left uninitialized except for zeroing, resulting in it always being 
an all-zero byte array.&lt;/p&gt;
&lt;p&gt;Any data encrypted using public-key encryption 
in this release can be decrypted trivially by supplying an all-zero 
session key, fully compromising confidentiality.&lt;/p&gt;
&lt;p&gt;The vulnerability affects only public key encryption (PKESK packets).  Passphrase-based encryption (SKESK packets) is not affected.&lt;/p&gt;
&lt;p&gt;Root cause: Vulnerable session key buffer used in PKESK packet generation.&lt;/p&gt;
&lt;p&gt;The defect was introduced in commit `7bd9a8dc356aae756b40755be76d36205b6b161a` where initialization 
logic inside `encrypted_build_skesk()` only randomized the key for the 
SKESK path and omitted it for the PKESK path.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ribose RNP&lt;/p&gt;
&lt;p&gt;In RNP version 0.18.0 a refactoring regression causes the symmetric 
session key used for Public-Key Encrypted Session Key (PKESK) packets to
 be left uninitialized except for zeroing, resulting in it always being 
an all-zero byte array.&lt;/p&gt;
&lt;p&gt;Any data encrypted using public-key encryption 
in this release can be decrypted trivially by supplying an all-zero 
session key, fully compromising confidentiality.&lt;/p&gt;
&lt;p&gt;The vulnerability affects only public key encryption (PKESK packets).  Passphrase-based encryption (SKESK packets) is not affected.&lt;/p&gt;
&lt;p&gt;Root cause: Vulnerable session key buffer used in PKESK packet generation.&lt;/p&gt;
&lt;p&gt;The defect was introduced in commit `7bd9a8dc356aae756b40755be76d36205b6b161a` where initialization 
logic inside `encrypted_build_skesk()` only randomized the key for the 
SKESK path and omitted it for the PKESK path.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-13470</guid>
    </item>
  </channel>
</rss>
