Open Spivoxity opened 4 months ago
An anonymous "security researcher" reports various potential buffer overruns, none of them drastic.
runtime/loader.c
read_string
runtime/xmain.c
PATH
runtime/linker.c
LINE
No doubt there are other security problems, some of them more potentially serious than these.
An anonymous "security researcher" reports various potential buffer overruns, none of them drastic.
runtime/loader.c
, there is no check on the segment sizes read from the file trailer (which could even be negative!).runtime/loader.c
, the functionread_string
(used to read symbol names) has a fixed-size buffer that could overflow.runtime/xmain.c
, there is a fixed-size buffer for components of thePATH
environment variable that could overflow.runtime/linker.c
, there is a fixed-size buffer used to form symbols for theLINE
directive that could overflow.No doubt there are other security problems, some of them more potentially serious than these.