Closed Bug 157014 Opened 24 years ago Closed 24 years ago

History writes out a "last_page_visited" pref that corrupts prefs.js

Categories

(Core Graveyard :: History: Global, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 143459

People

(Reporter: bzbarsky, Assigned: bugzilla)

Details

Attachments

(1 file)

BUILD: 2002-07-03-21 linux trunk (but a problem with 1.0/1.1 as well). PROBLEM: History writes out the browser.history.last_page_visited as a char pref. Unfortunately, the string value of this pref can contain newlines. See also bug 143459. Attaching a testcase that shows untrusted content being able to corrupt a profile at will as a result of this bug.
This web page causes us to write out the browser.history.last_page_visited pref to the profile with a newline embedded in the value. This makes no prefs coming after "browser.history" in alphabetical order (ie most of them) be loaded.
Not good... marking security sensitive to avoid giving ideas to folks.
Group: security?
Keywords: mozilla1.1, nsbeta1+
OK, the fix for bug 143459 fixed this; I've filed bug 157653 on the remaining issues, which are not security-related at all. *** This bug has been marked as a duplicate of 143459 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Group: security
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: