{"id":119,"date":"2008-02-09T22:10:35","date_gmt":"2008-02-10T06:10:35","guid":{"rendered":"http:\/\/cubist.cs.washington.edu\/Security\/2008\/02\/09\/firefox-view-source-vulnerability\/"},"modified":"2008-02-09T22:10:35","modified_gmt":"2008-02-10T06:10:35","slug":"firefox-view-source-vulnerability","status":"publish","type":"post","link":"https:\/\/secblog.cs.washington.edu\/Security\/2008\/02\/09\/firefox-view-source-vulnerability\/","title":{"rendered":"Firefox &#8220;View-Source&#8221; Vulnerability"},"content":{"rendered":"<p>I thought that since most of us use Firefox people might care &#8211; apparently the default installation\/settings of Firefox&#8217;s latest release allow all scripts written on websites to be executed.\u00a0 I don&#8217;t know with what privileges the code executes, but presumably whatever privileges Firefox has. Anyway, it can be disabled via the NoScript plugin (Or just don&#8217;t select &#8220;view-source&#8221;? The article&#8217;s not very clear on whether the exploited error was merely in the view-source mechanism, or whether the user must in fact click &#8220;view-source&#8221;).\u00a0 Either way, it&#8217;s cool that someone discovered the error in a release only several hours old as of this posting.<\/p>\n<p>The original, very brief blog post reporting this can be found <a href=\"http:\/\/it.slashdot.org\/it\/08\/02\/09\/2215205.shtml\">here<\/a> on slashdot.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I thought that since most of us use Firefox people might care &#8211; apparently the default installation\/settings of Firefox&#8217;s latest release allow all scripts written on websites to be executed.\u00a0 I don&#8217;t know with what privileges the code executes, but &hellip; <a href=\"https:\/\/secblog.cs.washington.edu\/Security\/2008\/02\/09\/firefox-view-source-vulnerability\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":45,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[],"class_list":["post-119","post","type-post","status-publish","format-standard","hentry","category-current-events"],"_links":{"self":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts\/119","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/users\/45"}],"replies":[{"embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/comments?post=119"}],"version-history":[{"count":0,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts\/119\/revisions"}],"wp:attachment":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/media?parent=119"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/categories?post=119"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/tags?post=119"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}