Closed
Bug 626377
Opened 14 years ago
Closed 8 months ago
Investigate if it was possible to automatically check dangerous use of raw nsI* pointers
Categories
(Core :: XPCOM, task)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: smaug, Unassigned)
Details
(Keywords: sec-audit, Whiteboard: [sg:audit])
There have been plenty of crashes because of raw nsI* pointers.
Bug 625311, Bug 588929, Bug 624187, etc.
Could we have some tool to check all the cases when raw nsI* is used as a
member of an object. Then, perhaps manually, mark somehow the safe ones and
fix others.
A problem is that once the code changes, the safe ones may become unsafe.
|
||
Updated•14 years ago
|
Whiteboard: [sg:audit]
Can we open this bug up? Public discussion of the issue might help and no specific vulnerability is outlined here.
|
|
||
Updated•9 years ago
|
Group: core-security → core-security-release
|
||
Updated•2 years ago
|
Severity: normal → S3
|
||
Updated•8 months ago
|
Type: defect → task
|
||
Comment 2•8 months ago
|
||
This would still be nice, but this never really went anywhere. I made some kind of attempt myself at once point.
Group: core-security-release
Status: NEW → RESOLVED
Closed: 8 months ago
Component: General → XPCOM
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•