Analysis failed in EMBArk only on dashboard about embark

[torabi12]

I checked again the above FWs and both were OK in EMBArk. Thank you!!

I wanted to scan an HP Docking Station's binary and I got a similar issue, according the logs all the things are fine but EMBArk displays a failure at the end like above.

FW file:
https://ftp.hp.com/pub/softpaq/sp100001-100500/sp100099.exe

I extracted it and I used the tesla_firmware_hp_Ver2_33_004.eeprom inside.

The logs from EMBArk:
HP-UltraSlim_EMBArk-logs.zip

Maybe it is not the best FW for scanning but it would be great to have the logs and to display the statistics on the dashboard which are missing now.

---

I would give a last example, maybe it helps. I wanted to scan an UEFI Bios for Dell PowerEdge server. The initial release from 2017 is here:
https://dl.dell.com/FOLDER04612973M/1/BIOS_DT5JM_WN64_1.2.11.EXE

I grabbed out the cap file and the scan was long, at least 5 hours in emba.

FwHunt had some fwhunt_scan_analyzer.py errors during the scan, but the report generated.
Logs from EMBArk:
emba_run.log
logreader.log

at the end I got failure on the page:

[torabi12]

I checked the compare with another openwrt firmware and the emba scan was ok with default-scan profile, but in EMBArk the analysis failed.
I used this file for testing:

https://downloads.openwrt.org/releases/18.06.0/targets/ar71xx/generic/openwrt-18.06.0-ar71xx-generic-wrt160nl-squashfs-factory.bin

I got failed in EMBArk:

and the Ubuntu's console displayed some errors during the scan:

[BenediktMKuehne]

Looking into it

[m-1-k-3]

The shown errors could be from s115 emulation module.

[BenediktMKuehne]

analysis works correctly, the problem seems to be in the post-processing

[m-1-k-3]

Should be solved by #93

[torabi12]

It is a mixed story but I found a similar test which was unfinished after 11 hours running. I wanted to scan an Asus motherboard's BIOS from here:
https://dlcdnets.asus.com/pub/ASUS/mb/LGA1151/H110M-A/H110M-A-ASUS-3805.zip
I used the CAP file inside: H110M-A-ASUS-3805.CAP
with Expert Mode, selecting all the categories on the page.

I followed the modules' status and S115 was not OK, maybe this file is not good for this modul:

I had some errors in the terminal:

The progress bar stuck at the end:

and there was no final state for the scan:

I did the same test in emba only using default-profile + CWE-search and there were no errors, I got the riport at the end.

If I select all the categories and the file under test is not suitable for a modul then maybe something goes wrong there, but if I specify a parameter for emba that does not result in a report page then the test still runs fine. In general my problem is that under EMBArk sometimes no result is obtained, even if the partial report is done, but it cannot be accessed from the page, only copied from the filesystem.
I just wanted to collect some problematic files which are easily testable with emba, but some issues can be happen under EMBArk.

This was the end in EMBArk:

The initial command under EMBArk uses the "-m s120" parameter for CWE-Search, but under emba it is "-c". I have found that under EMBArk, CWE-Search does not start because there is no start or end time in the log for this module.

If you need any retest or info from testing side for the above firmwares, please let me know and I will check the details if something is missing.