Closed
Bug 930066
Opened 11 years ago
Closed 10 years ago
Test coverage for cross-origin reflectors passed to CloneNonReflectors
Categories
(Core :: XPConnect, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1027131
People
(Reporter: bholley, Assigned: gkrizsanits)
References
Details
(Keywords: sec-other)
Otherwise, we'll end up with the same problem we have with COWs in bugs like bug 926712, whereby content sends a cross-origin object to chrome and convinces chrome to toString it.
This should be a simple 1-line fix to CloneNonReflectorsWrite. Gabor, can you take this?
Reporter | ||
Comment 1•11 years ago
|
||
Gabor points out that we probably already do this by virtue of unwrapping the security wrapper with a CheckedUnwrap before hitting the reflector. So let's just morph this bug into something to make sure we have test coverage for that.
Summary: CloneNonReflectors should do a subsumes check when writing an Xrayable into the buffer → Test coverage for cross-origin reflectors passed to CloneNonReflectors
Reporter | ||
Comment 2•10 years ago
|
||
I add this test coverage in the last patch in bug 1027131.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Updated•9 years ago
|
Group: core-security → core-security-release
Updated•9 years ago
|
Group: core-security-release
You need to log in
before you can comment on or make changes to this bug.
Description
•