<?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://db.gcve.eu</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, 11 Nov 2026 05:08:45 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-120295</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-120295</link>
      <description>&lt;p&gt;Incorrect Authorization vulnerability in the devices page bulk move in nerves-hub nerves_hub_web allows an authenticated user with the manage role in one organization and only the view role in another to move devices into the second organization&amp;#39;s product via the &amp;#34;Move device(s) to product&amp;#34; action. The target-product event in NervesHubWeb.Live.Devices.Index looks the product up with NervesHub.Products.get_by_id/2, which checks that the user is a member of the product&amp;#39;s organization at any role, and move-devices-product then changes each selected device&amp;#39;s organization and product. The device API&amp;#39;s move requires manage in the target organization, and an earlier fix added the check on the organization the devices leave but not on the one they enter.&lt;/p&gt;
&lt;p&gt;A moved device keeps its key and certificate, joins the target organization&amp;#39;s matching deployment groups, and is sent their firmware with a download URL, which the view role cannot otherwise obtain. The user cannot change or control devices that already belong to the other organization.&lt;/p&gt;
&lt;p&gt;This issue affects nerves_hub: from 1.0.0 before 2.5.3.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Incorrect Authorization vulnerability in the devices page bulk move in nerves-hub nerves_hub_web allows an authenticated user with the manage role in one organization and only the view role in another to move devices into the second organization&amp;#39;s product via the &amp;#34;Move device(s) to product&amp;#34; action. The target-product event in NervesHubWeb.Live.Devices.Index looks the product up with NervesHub.Products.get_by_id/2, which checks that the user is a member of the product&amp;#39;s organization at any role, and move-devices-product then changes each selected device&amp;#39;s organization and product. The device API&amp;#39;s move requires manage in the target organization, and an earlier fix added the check on the organization the devices leave but not on the one they enter.&lt;/p&gt;
&lt;p&gt;A moved device keeps its key and certificate, joins the target organization&amp;#39;s matching deployment groups, and is sent their firmware with a download URL, which the view role cannot otherwise obtain. The user cannot change or control devices that already belong to the other organization.&lt;/p&gt;
&lt;p&gt;This issue affects nerves_hub: from 1.0.0 before 2.5.3.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-120295</guid>
    </item>
  </channel>
</rss>
