{"id":31,"date":"2008-01-29T17:33:29","date_gmt":"2008-01-30T00:33:29","guid":{"rendered":"http:\/\/blog.mozilla.org\/security\/2008\/01\/29\/status-update-for-chrome-protocol-directory-traversal-issue\/"},"modified":"2008-01-29T17:33:29","modified_gmt":"2008-01-30T00:33:29","slug":"status-update-for-chrome-protocol-directory-traversal-issue","status":"publish","type":"post","link":"https:\/\/blog.mozilla.org\/security\/2008\/01\/29\/status-update-for-chrome-protocol-directory-traversal-issue\/","title":{"rendered":"Status update for Chrome Protocol Directory Traversal issue"},"content":{"rendered":"<p>Background on this issue is available <a href=\"http:\/\/blog.mozilla.org\/security\/2008\/01\/22\/chrome-protocol-directory-traversal\/\">here<\/a>.<\/p>\n<p><strong>Impact<\/strong><\/p>\n<p>An attacker can use this vulnerability to collect session information, including session cookies and session history.\u00a0 Firefox is not vulnerable by default.\u00a0 Only users that have installed &#8220;flat&#8221; packed add-ons are at risk.\u00a0 Discussion about &#8220;flat&#8221; packaged add-ons is <a href=\"https:\/\/bugzilla.mozilla.org\/show_bug.cgi?id=413549\">here<\/a>.\u00a0 A partial list of &#8220;flat&#8221; packed add-ons is available <a href=\"https:\/\/bugzilla.mozilla.org\/attachment.cgi?id=300181\">here<\/a>.\u00a0 If you are an author of any of these add-ons, please release an update to your add-on that uses .jar packaging.<\/p>\n<p>This bug is tracking the additional information: <a href=\"https:\/\/bugzilla.mozilla.org\/show_bug.cgi?id=413451\"><\/a><\/p>\n<p><a href=\"https:\/\/bugzilla.mozilla.org\/show_bug.cgi?id=413451\">https:\/\/bugzilla.mozilla.org\/show_bug.cgi?id=413451 <\/a><\/p>\n<p><strong>Status<\/strong><\/p>\n<p>Based on this new information Mozilla has changed the security severity rating to high.\u00a0 A fix is included in Firefox 2.0.0.12 which be available shortly.<br \/>\n<a href=\"https:\/\/bugzilla.mozilla.org\/show_bug.cgi?id=413250\"><\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Background on this issue is available here. Impact An attacker can use this vulnerability to collect session information, including session cookies and session history.\u00a0 Firefox is not vulnerable by default.\u00a0 &hellip; <a class=\"go\" href=\"https:\/\/blog.mozilla.org\/security\/2008\/01\/29\/status-update-for-chrome-protocol-directory-traversal-issue\/\">Read more<\/a><\/p>\n","protected":false},"author":48,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[30,69,77],"tags":[73],"coauthors":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v22.5 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Status update for Chrome Protocol Directory Traversal issue - Mozilla Security Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/blog.mozilla.org\/security\/2008\/01\/29\/status-update-for-chrome-protocol-directory-traversal-issue\/\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Window Snyder\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"1 minute\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/blog.mozilla.org\/security\/2008\/01\/29\/status-update-for-chrome-protocol-directory-traversal-issue\/\",\"url\":\"https:\/\/blog.mozilla.org\/security\/2008\/01\/29\/status-update-for-chrome-protocol-directory-traversal-issue\/\",\"name\":\"Status update for Chrome Protocol Directory Traversal issue - Mozilla Security Blog\",\"isPartOf\":{\"@id\":\"https:\/\/blog.mozilla.org\/security\/#website\"},\"datePublished\":\"2008-01-30T00:33:29+00:00\",\"dateModified\":\"2008-01-30T00:33:29+00:00\",\"author\":{\"@id\":\"https:\/\/blog.mozilla.org\/security\/#\/schema\/person\/bcfe8d4a8562282caf71ca487f4a36f5\"},\"breadcrumb\":{\"@id\":\"https:\/\/blog.mozilla.org\/security\/2008\/01\/29\/status-update-for-chrome-protocol-directory-traversal-issue\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/blog.mozilla.org\/security\/2008\/01\/29\/status-update-for-chrome-protocol-directory-traversal-issue\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/blog.mozilla.org\/security\/2008\/01\/29\/status-update-for-chrome-protocol-directory-traversal-issue\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/blog.mozilla.org\/security\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Status update for Chrome Protocol Directory Traversal issue\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/blog.mozilla.org\/security\/#website\",\"url\":\"https:\/\/blog.mozilla.org\/security\/\",\"name\":\"Mozilla Security Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/blog.mozilla.org\/security\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/blog.mozilla.org\/security\/#\/schema\/person\/bcfe8d4a8562282caf71ca487f4a36f5\",\"name\":\"Window Snyder\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/blog.mozilla.org\/security\/#\/schema\/person\/image\/ac9103056fd345532d56198464860a0a\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/73de47c5d7f96fbe0d5058c37ae1fefc?s=96&d=identicon&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/73de47c5d7f96fbe0d5058c37ae1fefc?s=96&d=identicon&r=g\",\"caption\":\"Window Snyder\"},\"sameAs\":[\"http:\/\/blog.mozilla.org\/security\/\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Status update for Chrome Protocol Directory Traversal issue - Mozilla Security Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/blog.mozilla.org\/security\/2008\/01\/29\/status-update-for-chrome-protocol-directory-traversal-issue\/","twitter_misc":{"Written by":"Window Snyder","Est. reading time":"1 minute"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/blog.mozilla.org\/security\/2008\/01\/29\/status-update-for-chrome-protocol-directory-traversal-issue\/","url":"https:\/\/blog.mozilla.org\/security\/2008\/01\/29\/status-update-for-chrome-protocol-directory-traversal-issue\/","name":"Status update for Chrome Protocol Directory Traversal issue - Mozilla Security Blog","isPartOf":{"@id":"https:\/\/blog.mozilla.org\/security\/#website"},"datePublished":"2008-01-30T00:33:29+00:00","dateModified":"2008-01-30T00:33:29+00:00","author":{"@id":"https:\/\/blog.mozilla.org\/security\/#\/schema\/person\/bcfe8d4a8562282caf71ca487f4a36f5"},"breadcrumb":{"@id":"https:\/\/blog.mozilla.org\/security\/2008\/01\/29\/status-update-for-chrome-protocol-directory-traversal-issue\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.mozilla.org\/security\/2008\/01\/29\/status-update-for-chrome-protocol-directory-traversal-issue\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/blog.mozilla.org\/security\/2008\/01\/29\/status-update-for-chrome-protocol-directory-traversal-issue\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/blog.mozilla.org\/security\/"},{"@type":"ListItem","position":2,"name":"Status update for Chrome Protocol Directory Traversal issue"}]},{"@type":"WebSite","@id":"https:\/\/blog.mozilla.org\/security\/#website","url":"https:\/\/blog.mozilla.org\/security\/","name":"Mozilla Security Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/blog.mozilla.org\/security\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/blog.mozilla.org\/security\/#\/schema\/person\/bcfe8d4a8562282caf71ca487f4a36f5","name":"Window Snyder","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blog.mozilla.org\/security\/#\/schema\/person\/image\/ac9103056fd345532d56198464860a0a","url":"https:\/\/secure.gravatar.com\/avatar\/73de47c5d7f96fbe0d5058c37ae1fefc?s=96&d=identicon&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/73de47c5d7f96fbe0d5058c37ae1fefc?s=96&d=identicon&r=g","caption":"Window Snyder"},"sameAs":["http:\/\/blog.mozilla.org\/security\/"]}]}},"_links":{"self":[{"href":"https:\/\/blog.mozilla.org\/security\/wp-json\/wp\/v2\/posts\/31"}],"collection":[{"href":"https:\/\/blog.mozilla.org\/security\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.mozilla.org\/security\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.mozilla.org\/security\/wp-json\/wp\/v2\/users\/48"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.mozilla.org\/security\/wp-json\/wp\/v2\/comments?post=31"}],"version-history":[{"count":0,"href":"https:\/\/blog.mozilla.org\/security\/wp-json\/wp\/v2\/posts\/31\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.mozilla.org\/security\/wp-json\/wp\/v2\/media?parent=31"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.mozilla.org\/security\/wp-json\/wp\/v2\/categories?post=31"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.mozilla.org\/security\/wp-json\/wp\/v2\/tags?post=31"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/blog.mozilla.org\/security\/wp-json\/wp\/v2\/coauthors?post=31"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}