{"id":2337,"date":"2004-06-11T00:00:00","date_gmt":"2004-06-11T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2004\/06\/11\/cisco-warns-on-catalysis-dos-danger\/"},"modified":"2021-12-30T11:41:06","modified_gmt":"2021-12-30T11:41:06","slug":"cisco-warns-on-catalysis-dos-danger","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2004\/06\/11\/cisco-warns-on-catalysis-dos-danger\/","title":{"rendered":"Cisco warns on Catalysis DoS danger"},"content":{"rendered":"<p>Cisco has advised its customers to reconfigure or upgrade its Catalysis switch software after a flaw was discovered which could allow a denial of service (DoS) attack.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The flaw can be activated by sending an incomplete transmission control protocol (TCP) handshake and can bring down the switch.<\/p>\n<p>The Catalysis 6000, 5000, 4500 and 4000 series are all affected, as well as earlier switches that use the same code base.  The company said in a statement: &#8220;Cisco is aware that some versions of the Cisco CatOS software may be susceptible to a TCP DoS attack under certain circumstances.  Cisco has published a security advisory with mitigation techniques and free software upgrade information that may help customers protect themselves from potential exploitation.  To date, Cisco is not aware of any active exploitations of the vulnerability and is working closely with its customers to address this issue.&#8221;<\/p>\n<p>The flaw can be fixed by either a software patch or by reconfiguring the switch.<\/p>\n<p>Only users of Telnet, HTTP or SSH services are vulnerable.<\/p>\n<p>More info: http:\/\/www.vnunet.com\/news\/1155779<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[13],"tags":[],"class_list":["post-2337","post","type-post","status-publish","format-standard","hentry","category-warnings"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2337","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=2337"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2337\/revisions"}],"predecessor-version":[{"id":4824,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2337\/revisions\/4824"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=2337"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=2337"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=2337"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}