{"id":2390,"date":"2006-05-30T00:00:00","date_gmt":"2006-05-30T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2006\/05\/30\/macro-virus-aims-at-openoffice-staroffice\/"},"modified":"2021-12-30T11:41:15","modified_gmt":"2021-12-30T11:41:15","slug":"macro-virus-aims-at-openoffice-staroffice","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2006\/05\/30\/macro-virus-aims-at-openoffice-staroffice\/","title":{"rendered":"Macro virus aims at OpenOffice, StarOffice"},"content":{"rendered":"<p>An unknown virus writer has created the first macro virus that targets computers running the alternative word processors OpenOffice and StarOffice, antivirus firm Kaspersky Labs said on Tuesday.  Viruses that attack word processing applications have returned to center stage after the disappearance of macro viruses in 2000.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Sun Microsystems, the developer of StarOffice, has boasted in the past about the security of its software developed in collaboration with open-source projects.<\/p>\n<p>Stardust.A&#8217;s image loading functionality should work on any platform&#8211;Windows, Mac or Linux&#8211;on which OpenOffice and StarOffice run.<\/p>\n<p>http:\/\/www.securityfocus.com\/brief\/218?ref=rss<\/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-2390","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\/2390","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=2390"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2390\/revisions"}],"predecessor-version":[{"id":4877,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2390\/revisions\/4877"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=2390"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=2390"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=2390"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}