Re:Another flaw in Signal desktop app leaks chats in plaintext
by jrockway on Friday May 18, 2018 @07:23AM
(#17100504)
I mean, in C++ "=" could be called "dangerouslySetAribtraryMemoryLocation" and it would be just as accurate. In native code, even trivial operations like concatenating two strings or setting a variable can cause arbitrary code to execute.
[ Parent
| on HN ]
Re:Another flaw in Signal desktop app leaks chats in plaintext
by jhasse on Friday May 18, 2018 @08:41AM
(#17100939)
Care to give an example?
Re:Another flaw in Signal desktop app leaks chats in plaintext
by moefh on Friday May 18, 2018 @01:22PM
(#17103198)
Assuming OP was talking about overloading the '=' operator:
struct A {
int *p = nullptr;
A& operator=(int i) {
*p = i;
return *this;
}
};
int main(void)
{
A a;
a = 1; /* boom! */
return 0;
}
Re:Another flaw in Signal desktop app leaks chats in plaintext
by camgunz on Friday May 18, 2018 @01:21PM
(#17103191)
strcat (or, honestly, anything in string.h). strcat assumes its first argument has enough allocated space for the contents of the 2nd argument, and that the 2nd argument is NULL terminated. If either of those assumptions is wrong, strcat will overwrite memory, corrupting either your heap or your stack, both of which can lead to arbitrary code execution. It's laughably easy to do, so easy that even typing the letters `strcat` into your program is forbidden in basically every C/C++ shop.
Re:Another flaw in Signal desktop app leaks chats in plaintext
by jhasse on Saturday May 19, 2018 @01:37PM
(#17108841)
strcat is C and not C++ though.