-
Notifications
You must be signed in to change notification settings - Fork 565
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'master' into use-gzipped-preview
- Loading branch information
Showing
7 changed files
with
213 additions
and
11 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4,10 +4,40 @@ | |
|
||
### New Features | ||
|
||
### Breaking Changes | ||
|
||
### New Rules (0) | ||
|
||
- | ||
|
||
### Bug Fixes | ||
|
||
### capa explorer IDA Pro plugin | ||
|
||
### Development | ||
|
||
### Raw diffs | ||
- [capa v7.2.0...master](https://github.com/mandiant/capa/compare/v7.2.0...master) | ||
- [capa-rules v7.2.0...master](https://github.com/mandiant/capa-rules/compare/v7.2.0...master) | ||
|
||
### v7.2.0 | ||
capa v7.2.0 introduces a first version of capa explorer web: a web-based user interface to inspect capa results using your browser. Users can inspect capa result JSON documents in an online web instance or a standalone HTML page for offline usage. capa explorer supports interactive exploring of capa results to make it easier to understand them. Users can filter, sort, and see the details of all identified capabilities. capa explorer web was worked on by @s-ff as part of a [GSoC project](https://summerofcode.withgoogle.com/programs/2024/projects/cR3hjbsq), and it is available at https://mandiant.github.io/capa/explorer/#/. | ||
|
||
This release also adds a feature extractor for output from the DRAKVUF sandbox. Now, analysts can pass the resulting `drakmon.log` file to capa and extract capabilities from the artifacts captured by the sandbox. This feature extractor will also be added to the DRAKVUF sandbox as a post-processing script, and it was worked on by @yelhamer as part of a [GSoC project](https://summerofcode.withgoogle.com/programs/2024/projects/fCnBGuEC). | ||
|
||
Additionally, we fixed several bugs handling ELF files, and added the ability to filter capa analysis by functions or processes. We also added support to the IDA Pro extractor to leverage analyst recovered API names. | ||
|
||
Special thanks to our repeat and new contributors: | ||
* @lakshayletsgo for their first contribution in https://github.com/mandiant/capa/pull/2248 | ||
* @msm-cert for their first contribution in https://github.com/mandiant/capa/pull/2143 | ||
* @VascoSch92 for their first contribution in https://github.com/mandiant/capa/pull/2143 | ||
|
||
### New Features | ||
|
||
- webui: explore capa analysis results in a web-based UI online and offline #2224 @s-ff | ||
- support analyzing DRAKVUF traces #2143 @yelhamer | ||
- IDA extractor: extract names from dynamically resolved APIs stored in renamed global variables #2201 @Ana06 | ||
|
||
- cli: add the ability to select which specific functions or processes to analyze @yelhamer | ||
|
||
### Breaking Changes | ||
|
||
|
@@ -18,7 +48,6 @@ | |
- communication/socket/attach-bpf-to-socket-on-linux [email protected] | ||
- anti-analysis/anti-av/overwrite-dll-text-section-to-remove-hooks [email protected] | ||
- nursery/delete-file-on-linux [email protected] | ||
- | ||
|
||
### Bug Fixes | ||
|
||
|
@@ -34,8 +63,8 @@ | |
- CI: update build.yml workflow to exclude web and documentation files #2270 @s-ff | ||
|
||
### Raw diffs | ||
- [capa v7.1.0...master](https://github.com/mandiant/capa/compare/v7.1.0...master) | ||
- [capa-rules v7.1.0...master](https://github.com/mandiant/capa-rules/compare/v7.1.0...master) | ||
- [capa v7.1.0...7.2.0](https://github.com/mandiant/capa/compare/v7.1.0...7.2.0) | ||
- [capa-rules v7.1.0...7.2.0](https://github.com/mandiant/capa-rules/compare/v7.1.0...7.2.0) | ||
|
||
## v7.1.0 | ||
The v7.1.0 release brings large performance improvements to capa's rule matching engine. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -9,11 +9,27 @@ Use the `-t` option to run rules with the given metadata value (see the rule fie | |
For example, `capa -t [email protected]` runs rules that reference Willi's email address (probably as the author), or | ||
`capa -t communication` runs rules with the namespace `communication`. | ||
|
||
### only analyze selected functions | ||
Use the `--restrict-to-functions` option to extract capabilities from only a selected set of functions. This is useful for analyzing | ||
large functions and figuring out their capabilities and their address of occurance; for example: PEB access, RC4 encryption, etc. | ||
|
||
To use this, you can copy the virtual addresses from your favorite disassembler and pass them to capa as follows: | ||
`capa sample.exe --restrict-to-functions 0x4019C0,0x401CD0`. If you add the `-v` option then capa will extract the interesting parts of a function for you. | ||
|
||
### only analyze selected processes | ||
Use the `--restrict-to-processes` option to extract capabilities from only a selected set of processes. This is useful for filtering the noise | ||
generated from analyzing non-malicious processes that can be reported by some sandboxes, as well as reduce the execution time | ||
by not analyzing such processes in the first place. | ||
|
||
To use this, you can pick the PIDs of the processes you are interested in from the sandbox-generated process tree (or from the sandbox-reported malware PID) | ||
and pass that to capa as follows: `capa report.log --restrict-to-processes 3888,3214,4299`. If you add the `-v` option then capa will tell you | ||
which threads perform what actions (encrypt/decrypt data, initiate a connection, etc.). | ||
|
||
### IDA Pro plugin: capa explorer | ||
Please check out the [capa explorer documentation](/capa/ida/plugin/README.md). | ||
|
||
### save time by reusing .viv files | ||
Set the environment variable `CAPA_SAVE_WORKSPACE` to instruct the underlying analysis engine to | ||
cache its intermediate results to the file system. For example, vivisect will create `.viv` files. | ||
Subsequently, capa may run faster when reprocessing the same input file. | ||
This is particularly useful during rule development as you repeatedly test a rule against a known sample. | ||
This is particularly useful during rule development as you repeatedly test a rule against a known sample. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters