Closed Bug 194436 Opened 22 years ago Closed 14 years ago

XPConnect security review action items

Categories

(Core :: XPConnect, defect)

Product:
Core
Component:
XPConnect
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME
Milestone:
mozilla1.7alpha

People

(Reporter: hjtoi-bugzilla, Assigned: dbradley)

References

Details

(Whiteboard: [sg:investigation]) 

Modify JS engine so that XPConnect can directly monitor object creation and
deletion, helps with double free problems, perf etc.?

We should make it impossible to run code in safe context

Is it possible we might elevate privileges during GC?

SOAP generates stuff dynamically, some names can be easily guessed

Is it possible to generate JS exceptions that cross the chrome boundary and end
up being run with chrome privileges?
I'm going to start creating bugs off this as I find them.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.4beta
Whiteboard: [sg:investigation]
Depends on: 202889
Just a note, bug 202889 deals with issue one. I believe issue one incorrectly
states object, it should talk about JSContexts. We already know when JS objects
are finalized and we don't really need to know when they are created.
Target Milestone: mozilla1.4beta → mozilla1.5alpha
Target Milestone: mozilla1.5alpha → mozilla1.5beta
Moving out, speak up if you believe this needs to be considered for 1.5b
Target Milestone: mozilla1.5beta → mozilla1.6alpha
Moving out
Target Milestone: mozilla1.6alpha → mozilla1.7alpha
Group: core-security
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.