Closed
Bug 140133
Opened 23 years ago
Closed 23 years ago
Stack overrun in nsMsgi18n.cpp
Categories
(Core :: Security, defect)
Core
Security
Tracking
()
VERIFIED
FIXED
mozilla1.0
People
(Reporter: security-bugs, Assigned: security-bugs)
Details
(Keywords: topembed, Whiteboard: [adt1] [ETA 04/26])
Attachments
(1 file)
1022 bytes,
patch
|
nhottanscp
:
review+
hjtoi-bugzilla
:
superreview+
|
Details | Diff | Splinter Review |
http://lxr.mozilla.org/seamonkey/source/mailnews/base/util/nsMsgI18N.cpp
545 static char charset[kMAX_CSNAME+1];
546 char buffer[512];
...
580 token = nsCRT::strtok(cp, seps, &newStr);
581 if (token != NULL)
582 {
583 PL_strcpy(charset, token);
584 }
as you may see this is a classical stack overrun.
An exploit path I have so found is the following - attach char.html to html
new html message and send it - actual result crash.
Definitely exploitable - charset is on the stack - the easiest buffer
overflow.
(gdb) frame 3
Cannot access memory at address 0x47474747
(gdb)
Assignee | ||
Comment 1•23 years ago
|
||
Assignee | ||
Updated•23 years ago
|
Status: NEW → ASSIGNED
Keywords: nsbeta1
Whiteboard: patch, edt, adt, topembed
Target Milestone: --- → mozilla1.0
Comment 2•23 years ago
|
||
Comment on attachment 81027 [details] [diff] [review]
Patch - add bounds checking and null-termination
r=nhotta
Attachment #81027 -
Flags: review+
Comment 3•23 years ago
|
||
Comment on attachment 81027 [details] [diff] [review]
Patch - add bounds checking and null-termination
a=asa (on behalf of drivers) for checkin to the 1.0 branch.
Attachment #81027 -
Flags: approval+
Updated•23 years ago
|
Attachment #81027 -
Flags: approval+ → superreview+
Comment on attachment 81027 [details] [diff] [review]
Patch - add bounds checking and null-termination
sr=heikki
Comment 5•23 years ago
|
||
adding adt1.0.0+. Please check this in as soon as possible after getting
drivers approval and add the fixed1.0.0 keyword.
Updated•23 years ago
|
Comment 6•23 years ago
|
||
Mitch, could you check this into the branch today and mark this fixed1.0.0?
Assignee | ||
Comment 7•23 years ago
|
||
Fixed, on trunk and 1.0 branch.
Verified on 2002-04-30-trunk on WinNT.
Marking verified as per above developer comments.
Status: RESOLVED → VERIFIED
Verified on 2002-04-30-branch on WinNT.
Marking verified as per developer comments.
Keywords: fixed1.0.0 → verified1.0.0
Assignee | ||
Updated•22 years ago
|
Group: security?
You need to log in
before you can comment on or make changes to this bug.
Description
•