{"id":230783,"date":"2017-07-27T17:27:01","date_gmt":"2017-07-27T21:27:01","guid":{"rendered":"http:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/uncategorized\/cisco-bugs-leave-network-automation-vulnerable-to-attack-the-register.php"},"modified":"2017-07-27T17:27:01","modified_gmt":"2017-07-27T21:27:01","slug":"cisco-bugs-leave-network-automation-vulnerable-to-attack-the-register","status":"publish","type":"post","link":"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/automation\/cisco-bugs-leave-network-automation-vulnerable-to-attack-the-register.php","title":{"rendered":"Cisco bugs leave network automation vulnerable to attack &#8211; The Register"},"content":{"rendered":"<p><p>    A slip in certificate handling is one of three bugs in Cisco's    Autonomic Networking software.  <\/p>\n<p>    As its name implies, Autonomic Networking is about reducing the    load on network administrators by offering self-management for    suitable switches and routers under suitable versions of the    IOS operating system.  <\/p>\n<p>    And then, as they say, the murders began: Autonomous Networking    uses infrastructure certificates to verify nodes in the system,    and that's where the problem has emerged.  <\/p>\n<p>    It starts with     this advisory: a mistake in infrastructure certificate    revocation.  <\/p>\n<p>    In Cisco IOS XE, the bug could let an unauthenticated, remote    autonomic node back into a network after its certificate has    been revoked.  <\/p>\n<p>    That's because the software doesn't transfer certificate    revocation lists across Autonomic Control Plane Channels (ACP).    An attacker with access to the remote node, even if its    certificate has been revoked, can re-insert the revoked node    into the autonomic domain.  <\/p>\n<p>    The bug affects Release 16.x of Cisco IOS XE Software and are    configured to use Autonomic Networking.  <\/p>\n<p>    The only option for affected admins is to manually check that    the bad node's certificate has been deleted properly, and    then update the Autonomic Networking whitelist file.  <\/p>\n<p>    The other Autonomic Networking bugs in the collection are an        information disclosure vulnerability, and a     denial-of-service vulnerability.  <\/p>\n<p>    In the first, the information disclosure is only available to    an unauthenticated, adjacent attacker to view control plane    packets in clear text. So far, there's no fix available.  <\/p>\n<p>    In the second, attackers can crash adjacent IOS and IOS XE    Autonomic Networking nodes. Cisco doesn't yet know what causes    the bug, but if an attacker captured packets (exploiting the    information disclosure bug, for example), they can replay them    to reset the ACP channel of the system. Again, users will have    to keep an eye out for when a fix lands.   <\/p>\n<p>    Sponsored:     The Joy and Pain of Buying IT - Have Your Say  <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>View original post here:<\/p>\n<p><a target=\"_blank\" rel=\"nofollow\" href=\"https:\/\/www.theregister.co.uk\/2017\/07\/27\/cisco_bugs_leave_network_automation_vulnerable_to_attack\/\" title=\"Cisco bugs leave network automation vulnerable to attack - The Register\">Cisco bugs leave network automation vulnerable to attack - The Register<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> A slip in certificate handling is one of three bugs in Cisco's Autonomic Networking software. As its name implies, Autonomic Networking is about reducing the load on network administrators by offering self-management for suitable switches and routers under suitable versions of the IOS operating system. And then, as they say, the murders began: Autonomous Networking uses infrastructure certificates to verify nodes in the system, and that's where the problem has emerged <a href=\"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/automation\/cisco-bugs-leave-network-automation-vulnerable-to-attack-the-register.php\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"limit_modified_date":"","last_modified_date":"","_lmt_disableupdate":"","_lmt_disable":"","footnotes":""},"categories":[431581],"tags":[],"class_list":["post-230783","post","type-post","status-publish","format-standard","hentry","category-automation"],"modified_by":null,"_links":{"self":[{"href":"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/wp-json\/wp\/v2\/posts\/230783"}],"collection":[{"href":"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/wp-json\/wp\/v2\/comments?post=230783"}],"version-history":[{"count":0,"href":"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/wp-json\/wp\/v2\/posts\/230783\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/wp-json\/wp\/v2\/media?parent=230783"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/wp-json\/wp\/v2\/categories?post=230783"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/wp-json\/wp\/v2\/tags?post=230783"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}