| Issue 53: | SRPC Shared Memory Infoleak / Memory corruption | |
| 3 people starred this issue and may be notified of changes. | Back to list |
Sign in to add a comment
|
Team: Beached As An Integer overflow vulnerability exists within the SharedMemory implementation of the browser plugin. Specifically, when read() is called on a shared memory object, an overly large offset can result in a memory leak, and an overly large length parameter can result in memory corruption |
||||||||||
,
Mar 12, 2009
Verified as an issue.
Status: Accepted
Owner: s...@google.com Labels: Type-Defect |
|||||||||||
,
Apr 10, 2009
Fix was released in build 57.
Status: Fixed
|
|||||||||||
|
|
|||||||||||