If you like any Car and Want to Buy please Call us 24/7

0344-2668711

Want to sale a Car: CLICK HERE

C++ Std::String Buffer Overflow And Integer Overflow

Interators are usually implemented using signed integers like the typical "for (int i=0; ..." and in fact is the type used indexing "cstr[i]", most of methods use the signed int, int by default is signed.
Nevertheless, the "std::string::operator[]" index is size_t which is unsigned, and so does size(), and same happens with vectors.
Besides the operator[] lack of negative index control, I will explain this later.

Do the compilers doesn't warn about this?


If his code got a large input it would index a negative numer, let see g++ and clang++ warnings:



No warnings so many bugs out there...

In order to reproduce the crash we can load a big string or vector from file, for example:


I've implemented a loading function, getting the file size with tellg() and malloc to allocate the buffer, then in this case used as a string.
Let see how the compiler write asm code based on this c++ code.



So the string constructor, getting size and adding -2 is clear. Then come the operator<< to concat the strings.
Then we see the operator[] when it will crash with the negative index.
In assembly is more clear, it will call operator[] to get the value, and there will hapen the magic dereference happens. The operator[] will end up returning an invalid address that will crash at [RAX]



In gdb the operator[] is a  allq  0x555555555180 <_znst7__cxx1112basic_stringicst11char_traitsicesaiceeixem plt="">

(gdb) i r rsi
rsi            0xfffffffffffefffe  -65538


The implmementation of operator ins in those functions below:

(gdb) bt
#0  0x00007ffff7feebf3 in strcmp () from /lib64/ld-linux-x86-64.so.2
#1  0x00007ffff7fdc9a5 in check_match () from /lib64/ld-linux-x86-64.so.2
#2  0x00007ffff7fdce7b in do_lookup_x () from /lib64/ld-linux-x86-64.so.2
#3  0x00007ffff7fdd739 in _dl_lookup_symbol_x () from /lib64/ld-linux-x86-64.so.2
#4  0x00007ffff7fe1eb7 in _dl_fixup () from /lib64/ld-linux-x86-64.so.2
#5  0x00007ffff7fe88ee in _dl_runtime_resolve_xsavec () from /lib64/ld-linux-x86-64.so.2
#6  0x00005555555554b3 in main (argc=2, argv=0x7fffffffe118) at main.cpp:29

Then crashes on the MOVZX EAX, byte ptr [RAX]

Program received signal SIGSEGV, Segmentation fault.
0x00005555555554b3 in main (argc=2, argv=0x7fffffffe118) at main.cpp:29
29     cout << "penultimate byte is " << hex << s[i] << endl;
(gdb)


What about negative indexing in std::string::operator[] ?
It's exploitable!

In a C char array is known that having control of the index, we can address memory.
Let's see what happens with C++ strings:






The operator[] function call returns the address of string plus 10, and yes, we can do abitrary writes.



Note that gdb displays by default with at&t asm format wich the operands are in oposite order:


And having a string that is in the stack, controlling the index we can perform a write on the stack.



To make sure we are writing outside the string, I'm gonna do 3 writes:


 See below the command "i r rax" to view the address where the write will be performed.


The beginning of the std::string object is 0x7fffffffde50.
Write -10 writes before the string 0x7fffffffde46.
And write -100 segfaults because is writting in non paged address.



So, C++ std::string probably is not vulnerable to buffer overflow based in concatenation, but the std::string::operator[] lack of negative indexing control and this could create vulnerable and exploitable situations, some times caused by a signed used of the unsigned std::string.size()










More articles


  1. Pentest Tools Apk
  2. Nsa Hack Tools
  3. Pentest Tools Download
  4. Nsa Hacker Tools
  5. Game Hacking
  6. Hack Tools For Games
  7. Android Hack Tools Github
  8. Growth Hacker Tools
  9. Pentest Tools Url Fuzzer
  10. Termux Hacking Tools 2019
  11. Bluetooth Hacking Tools Kali
  12. Hacking Tools Online
  13. Tools 4 Hack
  14. Hacker Tools Free Download
  15. Easy Hack Tools
  16. Hacking Tools For Games
  17. Hack Tools For Mac
  18. Hacking Tools Kit
  19. Pentest Tools For Windows
  20. Hacker Search Tools
  21. Pentest Tools Website Vulnerability
  22. Hacker Tools Github
  23. Hacker Techniques Tools And Incident Handling
  24. Pentest Tools Download
  25. Hacker Tools Free
  26. Beginner Hacker Tools
  27. Pentest Tools Free
  28. Hacking Tools Windows 10
  29. Pentest Reporting Tools
  30. Hacking Tools Hardware
  31. Hacker Tool Kit
  32. Hacker Tools 2020
  33. Hack Tools Online
  34. Hacking Tools Hardware
  35. Pentest Tools For Android
  36. Hack Tools
  37. What Are Hacking Tools
  38. Pentest Tools Kali Linux
  39. Pentest Tools Port Scanner
  40. Hacker Search Tools
  41. Hacking Tools Github
  42. Hack Tools For Mac
  43. Pentest Tools Alternative
  44. Pentest Tools List
  45. Hacker Tools Apk
  46. Wifi Hacker Tools For Windows
  47. Pentest Box Tools Download
  48. Hack Tools Download
  49. Hacking Tools For Windows Free Download
  50. Physical Pentest Tools
  51. Pentest Recon Tools
  52. Hack Tools Mac
  53. Hacker Tool Kit
  54. Beginner Hacker Tools
  55. Hacking Tools Hardware
  56. Hacker Tools For Ios
  57. Hacker Tools Linux
  58. Hacker Security Tools
  59. Nsa Hack Tools
  60. Hacker Techniques Tools And Incident Handling
  61. Pentest Recon Tools
  62. Hacker
  63. Hacker Tools Apk
  64. How To Hack
  65. Hacker Search Tools
  66. Hacking Tools Mac
  67. Hacker Tools Online
  68. Pentest Tools Alternative
  69. Pentest Tools Online
  70. Hack Rom Tools
  71. Pentest Tools Download
  72. Hack Tools Mac
  73. New Hack Tools
  74. Hacking Tools Hardware
  75. Hack Tools Mac
  76. Pentest Tools Apk

0 comments:

Post a Comment