bug-make
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #45050] Invalid read / heap overflow in unescape_char()


From: Hanno Boeck
Subject: [bug #45050] Invalid read / heap overflow in unescape_char()
Date: Thu, 07 May 2015 22:12:03 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.60 Safari/537.36

URL:
  <http://savannah.gnu.org/bugs/?45050>

                 Summary: Invalid read / heap overflow in unescape_char()
                 Project: make
            Submitted by: hanno
            Submitted on: Fri 08 May 2015 12:12:01 AM CEST
                Severity: 3 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
       Component Version: None
        Operating System: None
           Fixed Release: None
           Triage Status: None

    _______________________________________________________

Details:

Attached file will cause a heap overflow / invalid read error in make. This
can be seen with address sanitizer or valgrind.

I'll attach Address Sanitizer output. This was found with american fuzzy lop.



    _______________________________________________________

File Attachments:


-------------------------------------------------------
Date: Fri 08 May 2015 12:12:01 AM CEST  Name:
Makefile.heapoverflow-unescape_char  Size: 3B   By: hanno

<http://savannah.gnu.org/bugs/download.php?file_id=33960>
-------------------------------------------------------
Date: Fri 08 May 2015 12:12:01 AM CEST  Name:
Makefile.heapoverflow-unescape_char.asan.txt  Size: 3kB   By: hanno

<http://savannah.gnu.org/bugs/download.php?file_id=33961>

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?45050>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]