Most existing conventional security mechanisms are insufficient, mainly attributable to their requirements for heavy processing capacity, large protocol message size, and longer round trips, for resource-intensive devices operating in an Internet of Things (IoT) context. These devices necessitate efficient communication and security protocols that are cognizant of the severe resource restrictions regarding energy, computation, communication, and storage. To realize this, the IETF (Internet Engineering Task Force) is currently working towards standardizing an ephemeral key-based lightweight and authenticated key exchange protocol called EDHOC (Ephemeral Diffie–Hellman over COSE). The protocol’s primary purpose is to build an OSCORE (Object Security for Constrained RESTful Environments) security environment by supplying crucial security properties such as secure key exchange, mutual authentication, perfect forward secrecy, and identity protection. EDHOC will most likely dominate IoT security once it becomes a standard. It is, therefore, imperative to inspect the protocol for any security flaw. In this regard, two previous studies have shown different security vulnerabilities of the protocol using formal security verification methods. Yet, both missed the vital security flaws we found in this paper: resource exhaustion and privacy attacks. In finding these vulnerabilities, we leveraged BAN-Logic and AVISPA to formally verify both EDHOC protocol variants. Consequently, we described these security flaws together with the results of the related studies and put forward recommended solutions as part of our future work.

中文翻译：

---

使用正式方法检查物联网环境中 Ephemeral Diffie-Hellman over COSE (EDHOC) 的漏洞

大多数现有的传统安全机制是不够的，主要是由于它们对在物联网 (IoT) 环境中运行的资源密集型设备的处理能力大、协议消息大小大和往返时间长的要求。这些设备需要高效的通信和安全协议，这些协议认识到能源、计算、通信和存储方面的严重资源限制。为了实现这一点，IETF（互联网工程任务组）目前正致力于标准化一种称为 EDHOC（Epheral Diffie-Hellman over COSE）的基于临时密钥的轻量级和经过身份验证的密钥交换协议。该协议的主要目的是通过提供关键的安全属性（例如安全密钥交换、相互身份验证、完美前向保密和身份保护）来构建 OSCORE（受约束 RESTful 环境的对象安全）安全环境。一旦成为标准，EDHOC 很可能会主导物联网安全。因此，必须检查协议是否存在任何安全漏洞。在这方面，之前的两项研究表明，使用形式安全验证方法的协议存在不同的安全漏洞。然而，两者都忽略了我们在本文中发现的重要安全漏洞：资源枯竭和隐私攻击。在发现这些漏洞时，我们利用 BAN-Logic 和 AVISPA 来正式验证两种 EDHOC 协议变体。最后，