{"id":4641,"date":"2025-09-03T02:05:35","date_gmt":"2025-09-03T02:05:35","guid":{"rendered":"https:\/\/cybersecurityinfocus.com\/?p=4641"},"modified":"2025-09-03T02:05:35","modified_gmt":"2025-09-03T02:05:35","slug":"warning-flaws-in-copeland-ot-controllers-can-be-leveraged-by-threat-actors","status":"publish","type":"post","link":"https:\/\/cybersecurityinfocus.com\/?p=4641","title":{"rendered":"Warning: Flaws in Copeland OT controllers can be leveraged by threat actors"},"content":{"rendered":"<div>\n<div class=\"grid grid--cols-10@md grid--cols-8@lg article-column\">\n<div class=\"col-12 col-10@md col-6@lg col-start-3@lg\">\n<div class=\"article-column__content\">\n<div class=\"container\"><\/div>\n<p>Experts have warned IT leaders for years that operational technology (OT) devices connected to the internet can have serious vulnerabilities that lead to network compromises. Tuesday, a security company disclosed the discovery of 10 holes in controllers from heating, cooling, and refrigeration system manufacturer Copeland LP that could allow a threat actor to disable or gain remote control of\u00a0 equipment, possibly damaging products and injuring people.<\/p>\n<p>Armis called the vulnerabilities in Copeland\u2019s E2 and E3 controllers \u201cFrostbyte10\u201d. <a href=\"https:\/\/media.armis.com\/rp-frostbyte10-executive-summary-en.pdf\" target=\"_blank\" rel=\"noopener\">Its report<\/a> was issued after Copeland released updated firmware version 2.31F01 for the devices, correcting the issues, which CSOs should ensure are promptly installed.<\/p>\n<p>The vulnerabilities, Armis said, \u201crepresented a potential high value target for attackers seeking to disrupt or ransom retail infrastructure providers.\u201d<\/p>\n<h2 class=\"wp-block-heading\">Move toward zero trust<\/h2>\n<p>\u201cThe flaws discovered could have allowed unauthorized actors to remotely manipulate parameters, disable systems, execute remote code, or gain unauthorized access to sensitive operational data. When combined and exploited, these vulnerabilities can result in unauthenticated remote code execution with root privileges,\u201d the report said.<\/p>\n<p>But perhaps the bigger news is the cause of one hole in the E3 firmware: a default admin user, \u201cONEDAY\u201d, with a daily generated password that, in an unpatched system, can be predictably generated by a threat actor (the bug is designated <a href=\"https:\/\/cvefeed.io\/vuln\/detail\/CVE-2025-6519\" target=\"_blank\" rel=\"noopener\">CVE-2025-6519<\/a>). Default admin users and passwords are the bane of any OT or IT system. <a href=\"https:\/\/www.csoonline.com\/article\/4014095\/some-brother-printers-have-a-remote-code-execution-vulnerability-and-they-cant-fix-it.html?utm=hybrid_search\" target=\"_blank\" rel=\"noopener\">CSO recently reported on a default password issue with Brother printers. <\/a>\u00a0<\/p>\n<p>Other E3 vulnerabilities can allow a threat actor to authenticate by obtaining only a password hash, or to get all usernames and password hashes for the application services through an API call, or to access any file by uploading a specially crafted building floor plan.<\/p>\n<p>The vulnerability in E2 controllers is through the use of a proprietary protocol that allows for unauthenticated file operations (<a href=\"https:\/\/nvd.nist.gov\/vuln\/detail\/CVE-2025-52551\" target=\"_blank\" rel=\"noopener\">CVE-2025-52551<\/a>).<\/p>\n<p>\u201cGuessable or predictable passwords embedded in OT devices are common,\u201d <a href=\"https:\/\/www.digitaldefence.ca\/company\/\" target=\"_blank\" rel=\"noopener\">Robert Beggs<\/a>, head of Canadian incident response firm Digital Defence, said in an email to <em>CSO<\/em>. \u201cPersons responsible for the management of OT devices are focused on production and reliability of service, not security. As a result, you frequently encounter OT devices that are insecure.\u201d<\/p>\n<p>To ensure security, organizations have to move towards a zero trust architecture for deploying OT devices, Beggs said. That includes verifying user identity, enforcing multifactor authentication, supporting role-based access, and ensuring that all access to devices are securely monitored and logged.\u00a0\u00a0<\/p>\n<p><strong>Related content:<\/strong> <a href=\"https:\/\/www.csoonline.com\/article\/4048002\/88-of-cisos-struggle-to-implement-zero-trust.html\" target=\"_blank\" rel=\"noopener\">CISOs struggle to implement zero trust<\/a><\/p>\n<p>Asked for comment on the Armis report, Copeland sent a statement to <em>CSO<\/em> saying that safeguarding the quality and security of the company\u2019s products and customers\u2019\u00a0applications\u00a0\u201cis our top priority. Our E2 and E3 controllers have provided reliable service for more than two decades to hundreds of companies and across essential industries such as\u00a0food retail, refrigeration, industrial processing, and cold storage.\u00a0We actively partner with the global cybersecurity community to help us\u00a0continue to\u00a0improve our products and advance industrywide standards\u00a0as cybersecurity environments and threats continue to evolve and expand,\u201d the company said.\u00a0<\/p>\n<p>\u201cUpon being notified of\u00a0potential E2 and E3 vulnerabilities,\u00a0Copeland engineers\u00a0acted immediately\u00a0to\u00a0swiftly address\u00a0potential issues and\u00a0ensure our customers\u2019 systems remained secure,\u00a0while\u00a0maintaining\u00a0transparent communication with all potentially affected customers,\u201d Copeland continued. \u201cAt this time, there are no known exploits of the\u00a0potential\u00a0vulnerabilities. We strongly encourage our customers to apply the available patches promptly to ensure continued security.\u201d\u00a0<\/p>\n<h2 class=\"wp-block-heading\">\u2018Expected shortcomings\u2019<\/h2>\n<p>The E2 Facility Management System is designed to provide complete control of building and refrigeration systems, including compressor groups, condensers, walk-ins, HVAC units, and lighting, <a href=\"https:\/\/www.copeland.com\/en-us\/products\/controls-monitoring-systems\/facility-controls-electronics\/facility-and-system-controls\/e2-facility-management-system\" target=\"_blank\" rel=\"noopener\">Copeland said<\/a>.\u00a0\u00a0<\/p>\n<p><a href=\"https:\/\/www.copeland.com\/en-us\/products\/controls-monitoring-systems\/facility-controls-electronics\/facility-and-system-controls\/supervisory-controls-e3\" target=\"_blank\" rel=\"noopener\">The newer E3<\/a> system adds a built-in touch-screen display with a web-accessible interface and integration with Copeland\u2019s supervisory control software. The E3 system replaces the E2, which went end-of-life in October, 2024. However, some organizations may still be using E2 systems, and the use of an unauthenticated proprietary protocol in E2 controllers permits sensitive operations without any form of identity verification or encryption. \u201cThese are not just coding oversights,\u201d says Armis, \u201cthey represent structural risks that can persist in OT environments for years.\u201d<\/p>\n<p>The findings by Armis aren\u2019t uncommon, said Beggs. \u201cIn fact,\u201d he added, \u201cthey might fall under the umbrella of \u2018expected shortcomings.\u2019\u00a0 Until the most recent past, [OT] devices were judged primarily on whether or not they worked, and performed expected tasks.\u00a0They were not expected to provide secure functionality, and there was no reward or penalty for an insecure device.\u201d\u00a0<\/p>\n<h2 class=\"wp-block-heading\">Demand secure OT devices<\/h2>\n<p>Because of this, Beggs warned, \u201cif organizations don\u2019t demand secure devices, they will not be provided by the vendor.\u201d<\/p>\n<p><strong>Related content:<\/strong> <a href=\"https:\/\/www.csoonline.com\/article\/3526285\/navigating-the-future-of-ot-security.html\" target=\"_blank\" rel=\"noopener\">Navigating the future of OT security<\/a><\/p>\n<p>There have been changes lately in OT cybersecurity, he added, because customers are recognizing the security risks associated with internet-connected devices. But, he said, the changed perspective has to be matched by real changes in how OT devices are acquired and managed.<\/p>\n<p>First, he said, there has to be a requirement or client demand for secure operations. Second, the schism between IT and OT management has to be resolved.\u00a0\u201cIt is completely typical\u00a0to be asked to do a penetration test of the wired and wireless networks, and then be told to ignore the OT devices because they are managed by a different department,\u201d he said.<\/p>\n<p>Network tools (cybersecurity intelligence, automated inventory, security configuration and management, patching, reporting) have to include OT networks as well as the more common IT networks, Beggs stressed. And incident response processes have to embrace the OT network.<\/p>\n<p>\u201cPresently, the OT network is treated so differently from the IT network that security processes are rare,\u201d he said.\u00a0\u201cWhere they do exist, they are usually a duplicate of what is being offered on the IT network, increasing the cost and complexity of management.\u00a0 Overcoming the \u2018great schism\u2019 will reduce costs and potential liability for all users.\u201d<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Experts have warned IT leaders for years that operational technology (OT) devices connected to the internet can have serious vulnerabilities that lead to network compromises. Tuesday, a security company disclosed the discovery of 10 holes in controllers from heating, cooling, and refrigeration system manufacturer Copeland LP that could allow a threat actor to disable or [&hellip;]<\/p>\n","protected":false},"author":0,"featured_media":4642,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-4641","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-education"],"_links":{"self":[{"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=\/wp\/v2\/posts\/4641"}],"collection":[{"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=4641"}],"version-history":[{"count":0,"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=\/wp\/v2\/posts\/4641\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=\/wp\/v2\/media\/4642"}],"wp:attachment":[{"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=4641"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=4641"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=4641"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}