search

BinaryAnalysisPlatform / bap-toolkit

A collection of ready to use binary analysis tools
MIT License
55 stars 14 forks source link

primus-checks ELF64-ubuntu18.04-gui UNIX-System V other #3

Closed Soapmaze closed 4 years ago

Soapmaze commented 4 years ago

  1. What incidents are expected to be reported, in case of a false negative, or what incidents are reported but are not expected? What are the presumed locations of the weaknesses in the binary? -An attempt was made to analyze a binary with a CWE-125 vulnerability, but the vulnerability was not found. I tried to detect using primus-checks, but the bar did not run and the results of extension halt were only printed in the inserts file and ended. primus-checks_command_results

  2. Upload the binary if possible. cwe_125_bin.zip Source Code cwe_125_source.zip

  3. Upload all files generated by the check, i.e., log files, incidents, stdout, stderr, etc (some may be missing depending on a tool) incidents incidents.zip log log.zip

Additional Information

  1. The output of the following commands: bap --version bap_version.txt bap --llvm-version bap_llvm_version.txt bap list plugins bap_list_plugins.txt

  2. The set of symbols that bap detects in the binary bap ./binary -dsymbols > binary.symbols cwe_125_test_symbols.zip

ivg commented 4 years ago

Thanks for the report. The reason why the analysis doesn't even start is the https://github.com/BinaryAnalysisPlatform/bap/issues/1124 bug in 2.1.0 so you have to update to the latest version of bap (2.2.0~alpha) to enable it. But the weakness itself still won't be detected since right now we don't have an analysis that detects stack-based buffer overflows. We can only detect some class of the heap-based buffer overflows. We are working on stack-based overflows right now, so watch for updates.