<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/emb3d/10</id>
  <title>Most recent entries from emb3d</title>
  <updated>2026-11-22T14:03:46.142696+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/tid-412</id>
    <title>tid-412</title>
    <updated>2026-11-22T14:03:46.147596+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Some devices will allow for the forwarding of packets to other connected devices (e.g., routing, port forwarding, tunneling, VPN). If the device is used to forward or route communications, a threat actor could change the forwarding rules or routes. This feature could be used by the threat actor to either (i) disable required forwarding rules to prevent authorized communications or (ii) add new rules that allow unauthorized access to other devices. The threat actor could potentially use this to gain access to devices that are within protected networks or zones.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/tid-412"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/tid-411</id>
    <title>tid-411</title>
    <updated>2026-11-22T14:03:46.147714+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>The device utilizes a weak or insecure cryptographic protocol or algorithm that can be broken or undermined. This could allow the threat actor to extract plaintext information from encrypted communications, extract cryptographic keys, or bypass authentication mechanisms. A threat actor can utilize various techniques to manipulate these protocols, including brute-force guessing of keys or using cryptanalysis to decipher the text.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/tid-411"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/tid-410</id>
    <title>tid-410</title>
    <updated>2026-11-22T14:03:46.147757+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>While encrypting data can prevent a threat actor from directly obtaining the plaintext communication, a threat actor may be able to infer information about the device or communicated data through side-channel and metadata analysis of encrypted communication sessions. For example, a threat actor could use information about message lengths, sequences, and frequency to infer some or all of the plaintext content of messages.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/tid-410"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/tid-408</id>
    <title>tid-408</title>
    <updated>2026-11-22T14:03:46.147793+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Some devices do not adequately encrypt communications that includes operational or management information. Without adequate encryption, a threat actor can eavesdrop on the communications to gain access to device operational information, management information, or authentication information such as credentials or keys. Examples of popular protocols that lack encryption include FTP, Telnet, HTTP, Modbus, and DNP3.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/tid-408"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/tid-407</id>
    <title>tid-407</title>
    <updated>2026-11-22T14:03:46.147827+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Threat actors may be able to replay a message to a device to cause an unwanted function, send an unwanted command, or gain access to privileged data. Message replaying can be used to bypass nonexistent or poorly designed authentication mechanisms lacking proper protections, such as a nonce or timestamp.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/tid-407"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/tid-406</id>
    <title>tid-406</title>
    <updated>2026-11-22T14:03:46.147858+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Some devices operate using protocols that have no capacity for network-level authentication, connection, or creation of sessions on-device, therefore allowing a threat actor to establish malicious connections or send malicious data to the device. Authentication mechanisms include passwords and cryptographic keys/certificates.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/tid-406"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/tid-405</id>
    <title>tid-405</title>
    <updated>2026-11-22T14:03:46.147894+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Remote connections and communications can consume various device resources (e.g., network stack buffers, packet processing, socket connections) that, if exhausted, could lead to the device entering an unresponsive state. A threat actor may attempt to intentionally cause this by sending either repetitive or specially crafted messages to a device to consume resources and cause the device to become unresponsive. The unresponsive state will typically continue for at least the duration of the attack. In some cases, it may persist until the device is reset or rebooted, which may require physical operator presence.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/tid-405"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/tid-404</id>
    <title>tid-404</title>
    <updated>2026-11-22T14:03:46.147930+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Some devices will have operating modes that put the device in an inoperable state. Devices may also have network parsing or protocol vulnerabilities that can put the device in a deadlocked or otherwise unresponsive state. A threat actor may therefore be able to send a message to a device that causes it to enter one of these deadlocked or unresponsive states, rendering the device non-functional or leaving it in an otherwise degraded state. Additionally, if the device does not have a mechanism to reset or recover from this state, it may remain unavailable until it is reset or rebooted, which may require physical operator presence.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/tid-404"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/tid-401</id>
    <title>tid-401</title>
    <updated>2026-11-22T14:03:46.147966+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Some devices may support proprietary protocols, or may add proprietary functionality to open protocols. Many of the custom functions or commands may not be sufficiently documented. If users aren’t aware of these functions/commands, they cannot be expected to properly configure the device to remove unwanted functionality. Further, they are limited in their ability to monitor the device for any potential malicious use of these functions/commands to exploit devices.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/tid-401"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/tid-330</id>
    <title>tid-330</title>
    <updated>2026-11-22T14:03:46.148001+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Algorithms or code implementations of cryptographic processes will sometimes leak information by ending operations early or late based on, and correlated with, the input/key. If a threat actor is able to execute code on a processor performing a cryptographic operation, they may be able to infer the resulting key from that operation by measuring the timing it takes to perform the various functions.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/tid-330"/>
  </entry>
</feed>
