You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There was the absolute great #Hackersummercamp with our talks at BSidesLV, ICS Village (DEF CON) and Black Hat (Arsenal). The recording of the BSides talk is already available here. Beside this, Nate did a really great talk at BruCON – see here.
Beside a lot of code cleanup, bug fixing and some little improvements the new firmware diffing mode is one highlight in version 1.3.1.
In 1 day bug hunting, exploit development and the identification of silent patching it is quite common to identify the differences between two firmware releases.
To use this new feature (as usual in a very early alpha state) it is now possible to define a second firmware with the -o parameter. EMBA starts with some basic analysis of both firmware images, extracts both images and finds the differences between these firmware images:
If the file is some ASCII file a nice diff is shown:
If the file is a binary file we use radare2 for further analysis:
Beside your ongoing support with feedback, testing, working on issues and spreading EMBA you can now also support EMBA as a sponsor.
Check it out here and start being an essential part of the future of EMBA
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
What happened since the last EMBA release?
There was the absolute great #Hackersummercamp with our talks at BSidesLV, ICS Village (DEF CON) and Black Hat (Arsenal). The recording of the BSides talk is already available here. Beside this, Nate did a really great talk at BruCON – see here.
Beside a lot of code cleanup, bug fixing and some little improvements the new firmware diffing mode is one highlight in version 1.3.1.
In 1 day bug hunting, exploit development and the identification of silent patching it is quite common to identify the differences between two firmware releases.
To use this new feature (as usual in a very early alpha state) it is now possible to define a second firmware with the
-o
parameter. EMBA starts with some basic analysis of both firmware images, extracts both images and finds the differences between these firmware images:If the file is some ASCII file a nice diff is shown:
If the file is a binary file we use radare2 for further analysis:
For further details check our Wiki
Happy bug hunting :)
Beside your ongoing support with feedback, testing, working on issues and spreading EMBA you can now also support EMBA as a sponsor.
Check it out here and start being an essential part of the future of EMBA
What's Changed
Full Changelog: 1.3.0-AI-for-EMBA...1.3.1-diff-all-the-firmwares
This discussion was created from the release EMBA v1.3.1 - Diff it.
Beta Was this translation helpful? Give feedback.
All reactions