buffer-overflow

I am getting an exception System.IO.Internal.BufferOverflowException when I am trying to monitor a folder on network path(DFS - Distributed File System): To many changes at once . It works fine when FileSystemWatcher is monitoring local/network path that don't use this filesystem. I am able to get an event from 1000 + files on local path and I am not getting BufferOverflow exception, however when I am copying file to folder that is on DFS I am not even able to get an event from one(To clarify this, I am getting an error event raised...). I've already tried to set: fileSystemWatcher

I'm trying to execute this simple opcode for exit(0) call by overwriting the return address of main. The problem is I'm getting segmentation fault. #include <stdio.h> char shellcode[]= "/0xbb/0x14/0x00/0x00/0x00" "/0xb8/0x01/0x00/0x00/0x00" "/0xcd/0x80"; void main() { int *ret; ret = (int *)&ret + 2; // +2 to get to the return address on the stack (*ret) = (int)shellcode; } Execution result in Segmentation error. [user1@fedo BOF]$ gcc -o ExitShellCode ExitShellCode.c [user1@fedo BOF]$ ./ExitShellCode Segmentation fault (core dumped) This is the Objdump of the shellcode.a [user1@fedo BOF]$

I'm trying to figure out how stash smashing is carried out step by step. I have already used Google to no avail, I still don't know why my EIP is not being overwritten. I have this example program: 1 #include <stdio.h> 2 #include <string.h> 3 4 int main(int argc, char *argv[]) 5 { 6 char buf[10]; 7 8 strcpy(buf, argv[1]); 9 printf("Done.\n"); 10 return 0; 11 12 } It's compiled with gcc -g -o prog main.c When I put a lot of AAAAAA's I get SEGV and the register EBP (and also argc and argv addresses are overwritten: Program received signal SIGSEGV, Segmentation fault. 0x08048472 in main (argc=

I'm trying to bof a particular exploitme on DVL by redirecting input (to gets) using run < inputfile inside gdb I can overflow the program successfully but am having trouble appending hex values to the string.. I have tried quotations, converting the value of the mem addr to ascii and various escape attempts (\,\,\) with no luck Input file example: AAAA\x42 In the above example it would appear that the backslash is being read as an ascii char (5c) and the value 42 remains in the stack (oddly?). How would one go about specifying a hex value inside a gdb input file? Thanks Use perl! :) reader

Closed. This question is off-topic . It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 4 years ago . A long time ago when I was doing C++ work on Windows, there was an advanced diagnostics tool for debugging buffer overflows. It initialized all allocated memory areas, stack or heap, with a special pattern of characters so it could detect buffer overflows. It injected itself into the memory manager to do this and also so it could check all memory areas after a memory write to look for corruption. In exhaustive

I am converting double values to string like this: std::string conv(double x) { char buf[30]; sprintf(buf, "%.20g", x); return buf; } I have hardcoded the buffer size to 30, but am not sure if this is large enough for all cases. How can I find out the maximum buffer size I need? Does the precision get higher (and therefore buffer needs to increase) when switching from 32bit to 64? PS: I cannot use ostringstream or boost::lexical_cast for performance reason (see this ) I have hardcoded the buffer size to 30, but am not sure if this is large enough for all cases. It is. %.20g specifies 20 digits

Just curious, Is there or has anyone ever come across a heap / buffer overflow exception in C#? You can cause a buffer overflow in C# in unsafe code. For example: public unsafe struct testo { public int before; public fixed int items[16]; public int after; } testo x = new testo(); x.after = 1; for (int i = 0; i <= 16; ++i) { unsafe { x.items[i] = 99; } } Console.WriteLine(x.after); The above will print "99" because it overflowed the buffer. Absent unsafe code, I do not know of any way to cause a buffer overrun that doesn't trigger an exception. Depending on what you mean by Buffer overflow, an