Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug report on libhtp( AddressSanitizer: SEGV) #343

Closed
afosscontact opened this issue Dec 23, 2021 · 7 comments
Closed

Bug report on libhtp( AddressSanitizer: SEGV) #343

afosscontact opened this issue Dec 23, 2021 · 7 comments

Comments

@afosscontact
Copy link

afosscontact commented Dec 23, 2021

Describe the bug
A bug was found within the libhtp. Though it might not be an intended use of the relevant API, the bug can still produce critical issues within a program using libhtp. It would be best if the affected logic is checked beforehand.
The bug was found with a fuzzer based on the function "List.Expand1".
This may cause problems in the use of libraries

How To Reproduce

  1. Download the attached file
  2. Execute make_libhtp_bug2.sh
  3. ./test_all --gtest_filter=List.Expand1

==109414==ERROR: AddressSanitizer: SEGV on unknown address 0x7f023ae35468 (pc 0x0000007f2bb6 bp 0x7fff09e0b5f0 sp 0x7fff09e0b5d0 T0)
==109414==The signal is caused by a READ memory access.
#0 0x7f2bb6 in htp_list_array_get libhtp/htp/htp_list.c:106:25
#1 0x741808 in List_Expand1_Test::TestBody() libhtp/test/test_utils.cpp

Platform (please complete the following information):
OS: Ubuntu 18.04

libhtp_bug2.tar.gz

@attritionorg
Copy link

@afosscontact assimp?

@afosscontact
Copy link
Author

afosscontact commented Dec 23, 2021

I was sorry.
Project Name was wrong
I modified

@catenacyber
Copy link
Contributor

Thanks.
The commit to fix this c1e53f3

How did you find this bug ?
Did you try the tool on Suricata itself ? Could you ?

@catenacyber
Copy link
Contributor

By the way, side note for myself later, this is a good candidate for a CodeQL query...

@autofuzzoss
Copy link

Thank you for the fast fix
This bug found in Fuzzing technology we are studying
If you have completed the modification for this bug, I want to issue CVE ID
Is it possible to issue CVE ID?

@autofuzzoss
Copy link

If you are enabled, you want to be issued under the name Autofuzz.
Because I am being issued as a NickName called Autofuzz in CVEs found by this Fuzzing technology.

@catenacyber
Copy link
Contributor

Fixed by #344

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants