Heap disclosure in Windows libc for effectively forever. Reachable from some scripting languages too by using a similar code pattern:https://gist.github.com/gamozolabs/bef74c8aefc295e591514d97726d754e …
-
-
-
TL;DR: By writing 1 byte to the file (and thus stdio's internal buffer) the CRT incorrectly marks the entire internal buffer as valid, and thus all of it can be read. I reported this ~5 years ago and it was marked WONTFIX.
- Još 3 druga odgovora
Novi razgovor -
-
-
“Rustlang will kill all memory corruptions” they said. “See the world” they said.
- Još 4 druga odgovora
Novi razgovor -
-
-
Not sure if this counts under your definition - but my mind was pretty blown when classes of software became vulnerable just due to the compilation process:https://docs.microsoft.com/en-us/security-updates/SecurityAdvisories/2009/973882?redirectedfrom=MSDN …
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
I like the integer overflows inside standard memory allocators that make mere control of an allocation's size enough to virtually guarantee a subsequent heap overflow
- Još 1 odgovor
Novi razgovor -
-
-
How about the mingw64 libc snprintf not 0 terminating unless you set some magic undocumented define https://sourceforge.net/p/mingw-w64/bugs/709/ …
-
(CVE-2018-1000101)
Kraj razgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.