Closed Bug 568564 (CVE-2010-2754) Opened 14 years ago Closed 14 years ago

Suppress the script filename for cross-origin error events (SA39925)

Categories

(Core :: DOM: Core & HTML, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
Tracking Status
blocking2.0 --- beta1+
blocking1.9.2 --- needed
status1.9.2 --- .7-fixed
blocking1.9.1 --- needed
status1.9.1 --- .11-fixed

People

(Reporter: bzbarsky, Assigned: bzbarsky)

References

()

Details

(Keywords: fixed1.9.0.20, privacy, Whiteboard: [sg:moderate])

Attachments

(3 files)

Summary: Suppress the script filename for cross-origin error events → Suppress the script filename for cross-origin error events [Secunia Advisory SA39925]
In particular, we need to do that because on redirects we put the post-redirect URI into the JSScript filename field.  If js error reports had an origin not tied to filename, we could take various other approaches here.
Attached patch Like soSplinter Review
Attachment #447792 - Flags: review?(jst)
OS: Mac OS X → All
Hardware: x86 → All
Summary: Suppress the script filename for cross-origin error events [Secunia Advisory SA39925] → Suppress the script filename for cross-origin error events (SA39925)
Version: Trunk → unspecified
Shouldn't it block 3.6.4?
blocking1.9.1: --- → ?
blocking1.9.2: --- → ?
blocking2.0: --- → ?
Until it gets a sg evaluation it'll be needed but not hard blocking any of the upcoming branch releases; obviously would like a reviewed patch ASAP, but I know people's review queues are busy.
blocking1.9.1: ? → needed
blocking1.9.2: ? → needed
blocking2.0: ? → beta1+
Whiteboard: [sg:?]
Attachment #447792 - Flags: review?(jst) → review+
Keywords: privacy
Whiteboard: [sg:?] → [sg:low]
Whiteboard: [sg:low] → [sg:moderate]
The severity really depends on what information sites reveal through URLs.  

* http://0me.me/demo/XSUH/XSUH_demo_firefox_all_in_1.html got my Google profile ID, and thus a good guess at my email address.  That's a pretty bad privacy violation.

* In theory, a site might reveal a session token. If high-profile sites turned out to do that, we'd call this bug [sg:high].
Self-defense until fixed: block 3rd party cookies and the victim sites can't reveal any personal information.
Pushed http://hg.mozilla.org/mozilla-central/rev/155d4a2be1bc and then http://hg.mozilla.org/mozilla-central/rev/6043ca0d3fba to fix test issues.  Will create a roll-up patch for branches.
Status: NEW → RESOLVED
Closed: 14 years ago
Flags: in-testsuite+
Resolution: --- → FIXED
Attached patch 1.9.2 fixSplinter Review
Attachment #450044 - Flags: approval1.9.2.5?
Attached patch 1.9.1 mergeSplinter Review
Attachment #450045 - Flags: approval1.9.1.11?
Attachment #450044 - Flags: approval1.9.2.5? → approval1.9.2.6+
Comment on attachment 450045 [details] [diff] [review]
1.9.1 merge

a=LegNeato for 1.9.2.6 and 1.9.1.11. Please land this on mozilla-1.9.2 default and mozilla-1.9.1 default.
Attachment #450045 - Flags: approval1.9.1.11? → approval1.9.1.11+
is this really fixed? why 
http://secunia.com/community/forum/thread/show/4596/firefox_3_6_4_released
why is this happening (to me!)?

i mean, why secunia folks don't think this is fixed? it's their problem? it's mozilla's? is this a situation of ineffective communication?
It's fixed on the default 1.9.2 branch as stated, so will be in the next release, Firefox 3.6.7

If you're desperate for a preview build of it, get http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/3.6.7-candidates/build1/win32/en-US/Firefox%20Setup%203.6.7.exe
> is this really fixed?

Yes, but the fix hasn't been shipped yet.  It's fixed in the upcoming 1.9.2.x security release, as comment 16 says.
@Mardeg OK now I see the "clegnitto: approval1.9.2.7+". Sorry for my blindness. Thx for the info and the tip.

@bz thx!
Alias: CVE-2010-2754
Comment on attachment 450045 [details] [diff] [review]
1.9.1 merge

Requesting approval1.9.0.next on this patch so that we can take it in upcoming Camino 2.0.x security and stability updates.  If approved, I'll handle the checkins, unless the patch author requests otherwise.
Attachment #450045 - Flags: approval1.9.0.next?
Comment on attachment 450045 [details] [diff] [review]
1.9.1 merge

Approved for 1.9.0.20, a=dveditz
Attachment #450045 - Flags: approval1.9.0.next? → approval1.9.0.next+
Checking in content/base/test/test_bug461735.html;
/cvsroot/mozilla/content/base/test/test_bug461735.html,v  <--  test_bug461735.html
new revision: 1.2; previous revision: 1.1
done
Checking in dom/src/base/nsJSEnvironment.cpp;
/cvsroot/mozilla/dom/src/base/nsJSEnvironment.cpp,v  <--  nsJSEnvironment.cpp
new revision: 1.402; previous revision: 1.401
done
Keywords: fixed1.9.0.20
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: