Closed Bug 12182 Opened 25 years ago Closed 23 years ago

Review JS Console for historic attacks

Categories

(Core :: Security, defect, P3)

Product:
Core
Component:
Security
Platform:
All
Windows NT
Type:
defect

Tracking

()

Status:
VERIFIED FIXED
Milestone:
Future

People

(Reporter: norrisboyd, Assigned: security-bugs)

References

Details

The JS Console has had a number of historic attacks. Review the code to ensure
that it is secure against those attacks and others.
Status: NEW → ASSIGNED
Depends on: 4263
Blocks: 7252
No longer blocks: 7252
Blocks: 7252
Looks like a mid-air collision that wasn't detected - restoring dependency.
Target Milestone: M13
No JS Console at the moment. Vidur, is there a bug for creating a JS Console?
Target Milestone: M13 → M15
No JS console yet; postpone this bug.
Push security review tasks off until M16.
Target Milestone: M15 → M16
Bulk moving all Browser Security bugs to new Security: General component.  The 
previous Security component for Browser will be deleted.
Component: Security → Security: General
Target Milestone: M16 → M18
Changing Qa contact to myself.
QA Contact: dshea → junruh
Bulk reassigning most of norris's bugs to mstoltz.
Assignee: norris → mstoltz
Status: ASSIGNED → NEW
Status: NEW → ASSIGNED
Security reviews and denial-of-service attacks. These will be addressed in the 
post-beta2 timeframe (unless someone's interested in tackling them earlier?)

Assigning QA to czhang
QA Contact: junruh → czhang
Reassigning to jtaylor, who will be doing security reviews.
Assignee: mstoltz → jtaylor
Status: ASSIGNED → NEW
Status: NEW → ASSIGNED
JS console has a new implementation. Unsure if historic attacks are valid. -> 
mstoltz.
Assignee: jtaylor → mstoltz
Status: ASSIGNED → NEW
Future, because this deserves looking at but I don't anticipate any major 
exploits in the newly rewritten JS console, so this is not a ship-stop.
Status: NEW → ASSIGNED
Target Milestone: M18 → Future
QA Contact: czhang → junruh
Mass changing QA to ckritzer.
QA Contact: junruh → ckritzer
There's no way for a script to get a reference to the JS COnsole, so I don't
think there are any exploits to worry about. Jesse and I can't think of any
avenues of attack. We don't have a record of historic attacks against the 4.x JS
console, but my guess is they are all irrelevant now. Marking Fixed.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Marking VERIFIED FIXED per mstoltz's comments.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.