{"id":2305,"date":"2003-10-30T00:00:00","date_gmt":"2003-10-30T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2003\/10\/30\/security-flaws-make-macs-vulnerable-to-attacks\/"},"modified":"2021-12-30T11:41:02","modified_gmt":"2021-12-30T11:41:02","slug":"security-flaws-make-macs-vulnerable-to-attacks","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2003\/10\/30\/security-flaws-make-macs-vulnerable-to-attacks\/","title":{"rendered":"Security Flaws Make Macs Vulnerable To Attacks"},"content":{"rendered":"<p>Security research firm @stake is warning Macintosh users about three security problems with the Mac OS X 10.2.8 and previous versions.<\/p>\n<p>It ranks two of the flaws as high.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The first advisory, &#8220;Long argv[] Buffer Overflow,&#8221; warns that an attacker could possibly crash Mac OS X and execute commands as root.<\/p>\n<p>The Systemic Insecure File Permissions advisory states some applications on the vulnerable Mac OS X systems are installed with insecure file permissions and are globally writable.  This lets attackers with file-system access to an OS X machine replace binaries and obtain additional privileges from unsuspecting users, who may run the replaced version of the binary.<\/p>\n<p>The third vulnerability, Arbitrary File Overwrite via Core Files, enables attackers with certain access rights to overwrite arbitrary files and read certain files.<\/p>\n<p>There is no patch available for these vulnerabilities.<\/p>\n<p>An Apple Computer spokesperson could not say where the company would issue a fix, but Apple is working on a statement about the issue.<\/p>\n<p>More info: [url=http:\/\/www.informationweek.com\/story\/showArticle.jhtml;jsessionid=SJHW4MC3SCD14QSNDBGCKHQ?articleID=15800094]http:\/\/www.informationweek.com\/story\/showArticle.jhtml;jsessionid=SJHW4MC3SCD14QSNDBGCKHQ?articleID=15800094[\/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-2305","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\/2305","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=2305"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2305\/revisions"}],"predecessor-version":[{"id":4792,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2305\/revisions\/4792"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=2305"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=2305"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=2305"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}