<?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 05:51:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-31925 — Storage of clear text password in Brocade SANnav</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2023-31925</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Brocade SANnav&lt;/p&gt;
&lt;p&gt;Brocade
 SANnav before v2.3.0 and v2.2.2a stores SNMPv3 Authentication passwords
 in plaintext. A privileged user could retrieve these credentials with 
knowledge and access to these log files. SNMP 
credentials could be seen in SANnav SupportSave if the capture is 
performed after an SNMP configuration failure causes an SNMP 
communication log dump.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Brocade SANnav&lt;/p&gt;
&lt;p&gt;Brocade
 SANnav before v2.3.0 and v2.2.2a stores SNMPv3 Authentication passwords
 in plaintext. A privileged user could retrieve these credentials with 
knowledge and access to these log files. SNMP 
credentials could be seen in SANnav SupportSave if the capture is 
performed after an SNMP configuration failure causes an SNMP 
communication log dump.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2023-31925</guid>
    </item>
  </channel>
</rss>
