<?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>Tue, 06 Oct 2026 23:57:08 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-4128</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-4128</link>
      <description>EUVD-2026-4128</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-4128</guid>
    </item>
    <item>
      <title>fkie_cve-2024-24766</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-24766</link>
      <description>&lt;p&gt;CasaOS-UserService provides user management functionalities to CasaOS. Starting in version 0.4.4.3 and prior to version 0.4.7, the Casa OS Login page disclosed the username enumeration vulnerability in the login page. An attacker can enumerate the CasaOS username using the application response. If the username is incorrect application gives the error `**User does not exist**`.  If the password is incorrect application gives the error `**Invalid password**`.  Version 0.4.7 fixes this issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;CasaOS-UserService provides user management functionalities to CasaOS. Starting in version 0.4.4.3 and prior to version 0.4.7, the Casa OS Login page disclosed the username enumeration vulnerability in the login page. An attacker can enumerate the CasaOS username using the application response. If the username is incorrect application gives the error `**User does not exist**`.  If the password is incorrect application gives the error `**Invalid password**`.  Version 0.4.7 fixes this issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-24766</guid>
    </item>
    <item>
      <title>GHSA-c967-2652-gfjm — CasaOS Username Enumeration</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-c967-2652-gfjm</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/IceWhaleTech/CasaOS-UserService&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The Casa OS Login page has disclosed the username enumeration vulnerability in the login page.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;It is observed that the attacker can enumerate the CasaOS username using the application response. If the username is incorrect application gives the error &amp;#34;**User does not exist**&amp;#34;,  If the password is incorrect application gives the error &amp;#34;**Invalid password**&amp;#34;.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;Capture the login request in a tool like Burp Suit and use the intruder tab for trying multiple usernames. 
Keep checking the response of each request if the response says **Invalid password** then the username is right.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Using this error attacker can enumerate the username of CasaOS.&lt;/p&gt;
&lt;p&gt;### The logic behind the issue&lt;/p&gt;
&lt;p&gt;If the username is incorrect, then throw an error &amp;#34;User does not exist&amp;#34; else throw an error &amp;#34;Invalid password&amp;#34;.&lt;/p&gt;
&lt;p&gt;This condition can be vice versa like:&lt;/p&gt;
&lt;p&gt;If the password is incorrect, then throw an error &amp;#34;Invalid password&amp;#34; else throw an error &amp;#34;User does not exist&amp;#34;.&lt;/p&gt;
&lt;p&gt;### Mitigation&lt;/p&gt;
&lt;p&gt;Since this is the condition we have to implement a single error which can be &amp;#34;Username/Password is Incorrect!!!&amp;#34;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/IceWhaleTech/CasaOS-UserService&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The Casa OS Login page has disclosed the username enumeration vulnerability in the login page.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;It is observed that the attacker can enumerate the CasaOS username using the application response. If the username is incorrect application gives the error &amp;#34;**User does not exist**&amp;#34;,  If the password is incorrect application gives the error &amp;#34;**Invalid password**&amp;#34;.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;Capture the login request in a tool like Burp Suit and use the intruder tab for trying multiple usernames. 
Keep checking the response of each request if the response says **Invalid password** then the username is right.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Using this error attacker can enumerate the username of CasaOS.&lt;/p&gt;
&lt;p&gt;### The logic behind the issue&lt;/p&gt;
&lt;p&gt;If the username is incorrect, then throw an error &amp;#34;User does not exist&amp;#34; else throw an error &amp;#34;Invalid password&amp;#34;.&lt;/p&gt;
&lt;p&gt;This condition can be vice versa like:&lt;/p&gt;
&lt;p&gt;If the password is incorrect, then throw an error &amp;#34;Invalid password&amp;#34; else throw an error &amp;#34;User does not exist&amp;#34;.&lt;/p&gt;
&lt;p&gt;### Mitigation&lt;/p&gt;
&lt;p&gt;Since this is the condition we have to implement a single error which can be &amp;#34;Username/Password is Incorrect!!!&amp;#34;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-c967-2652-gfjm</guid>
    </item>
    <item>
      <title>gsd-2024-24766</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-24766</link>
      <description>gsd-2024-24766</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-24766</guid>
    </item>
  </channel>
</rss>
