{"id":2328,"date":"2004-01-12T00:00:00","date_gmt":"2004-01-12T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2004\/01\/12\/buffer-overflow-plugged-in-sun-one-web-server\/"},"modified":"2021-12-30T11:41:05","modified_gmt":"2021-12-30T11:41:05","slug":"buffer-overflow-plugged-in-sun-one-web-server","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2004\/01\/12\/buffer-overflow-plugged-in-sun-one-web-server\/","title":{"rendered":"Buffer Overflow Plugged in Sun ONE Web Server"},"content":{"rendered":"<p>In a brief alert, the Santa Clara, Calif.-based firm said the flaw could be exploited by a remote user to crash the Web server, which is a type of denial-of-service attack (define).<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Independent research firm Secunia has rated the security hole as &#8220;moderately critical.&#8221;<\/p>\n<p>The vulnerability affects the Sun ONE\/iPlanet Web Server 6.0 Service Pack 5 and earlier versions on the HP-UX platform.<\/p>\n<p>Sun has issued a new service pack to fix the flaw, noting that there are no workarounds.<\/p>\n<p>More info: [url=http:\/\/www.internetnews.com\/dev-news\/article.php\/3298031]http:\/\/www.internetnews.com\/dev-news\/article.php\/3298031[\/url]<\/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-2328","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\/2328","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=2328"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2328\/revisions"}],"predecessor-version":[{"id":4815,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2328\/revisions\/4815"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=2328"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=2328"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=2328"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}