Project overview: libmodbus
High level conclusions
Reachability and coverage overview
Project functions overview
The following table shows data about each function in the project. The functions included in this table correspond to all functions that exist in the executables of the fuzzers. As such, there may be functions that are from third-party libraries.
For further technical details on the meaning of columns in the below table, please see the Glossary .
| Func name | Functions filename | Args | Function call depth | Reached by Fuzzers | Fuzzers runtime hit | Func lines hit % | I Count | BB Count | Cyclomatic complexity | Functions reached | Reached by functions | Accumulated cyclomatic complexity | Undiscovered complexity |
|---|
Fuzzer details
Fuzzer: FuzzClient
Call tree
The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview
Call tree overview bitmap:
The distribution of callsites in terms of coloring is
| Color | Runtime hitcount | Callsite count | Percentage |
|---|---|---|---|
| red | 0 | 121 | 99.1% |
| gold | [1:9] | 0 | 0.0% |
| yellow | [10:29] | 0 | 0.0% |
| greenyellow | [30:49] | 1 | 0.81% |
| lawngreen | 50+ | 0 | 0.0% |
| All colors | 122 | 100 |
Fuzz blockers
The following nodes represent call sites where fuzz blockers occur.
| Amount of callsites blocked | Calltree index | Parent function | Callsite | Largest blocked function |
|---|---|---|---|---|
| 121 | 0 | EP | call site: 00000 | client |
Runtime coverage analysis
| Function name | source code lines | source lines hit | percentage hit |
|---|
Files reached
| filename | functions hit |
|---|---|
| fuzz/FuzzClient.c | 5 |
| src/modbus-tcp.c | 1 |
| src/modbus.c | 19 |
Fuzzer: FuzzServer
Call tree
The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview
Call tree overview bitmap:
The distribution of callsites in terms of coloring is
| Color | Runtime hitcount | Callsite count | Percentage |
|---|---|---|---|
| red | 0 | 25 | 44.6% |
| gold | [1:9] | 30 | 53.5% |
| yellow | [10:29] | 0 | 0.0% |
| greenyellow | [30:49] | 0 | 0.0% |
| lawngreen | 50+ | 1 | 1.78% |
| All colors | 56 | 100 |
Fuzz blockers
The followings are the branches where fuzzer fails to bypass.
| Unique non-covered Complexity | Unique Reachable Complexities | Unique Reachable Functions | All non-covered Complexity | All Reachable Complexity | Function Name | Function Callsite | Blocked Branch |
|---|---|---|---|---|---|---|---|
| 25 | 25 |
2 :
['__errno_location', 'modbus_strerror'] |
25 | 28 | server | call site: 00022 | /src/libmodbus/fuzz/FuzzServer.c:109 |
| 2 | 5 |
2 :
['modbus_free', '__errno_location'] |
2 | 5 | modbus_new_tcp | call site: 00018 | /src/libmodbus/src/modbus-tcp.c:904 |
| 2 | 2 |
1 :
['htonl'] |
10 | 10 | modbus_tcp_listen | call site: 00034 | /src/libmodbus/src/modbus-tcp.c:549 |
| 2 | 2 |
1 :
['__errno_location'] |
2 | 2 | modbus_tcp_listen | call site: 00029 | /src/libmodbus/src/modbus-tcp.c:514 |
| 2 | 2 |
1 :
['close'] |
2 | 2 | modbus_tcp_listen | call site: 00041 | /src/libmodbus/src/modbus-tcp.c:569 |
| 2 | 2 |
1 :
['__errno_location'] |
2 | 2 | modbus_tcp_accept | call site: 00043 | /src/libmodbus/src/modbus-tcp.c:698 |
| 2 | 2 |
1 :
['inet_ntop'] |
2 | 2 | modbus_tcp_accept | call site: 00045 | /src/libmodbus/src/modbus-tcp.c:715 |
| 2 | 2 |
1 :
['__errno_location'] |
2 | 2 | _modbus_tcp_select | call site: 00000 | /src/libmodbus/src/modbus-tcp.c:778 |
| 2 | 2 |
1 :
['__errno_location'] |
2 | 2 | modbus_receive | call site: 00049 | /src/libmodbus/src/modbus.c:527 |
| 0 | 0 | None | 142 | 158 | _modbus_receive_msg | call site: 00000 | /src/libmodbus/src/modbus.c:363 |
| 0 | 0 | None | 142 | 158 | _modbus_receive_msg | call site: 00000 | /src/libmodbus/src/modbus.c:371 |
| 0 | 0 | None | 142 | 158 | _modbus_receive_msg | call site: 00000 | /src/libmodbus/src/modbus.c:388 |
Runtime coverage analysis
| Function name | source code lines | source lines hit | percentage hit |
|---|
Files reached
| filename | functions hit |
|---|---|
| fuzz/FuzzServer.c | 3 |
| src/modbus-tcp.c | 3 |
| src/modbus.c | 8 |
| src/modbus-data.c | 1 |
Analyses and suggestions
Optimal target analysis
Remaining optimal interesting functions
The following table shows a list of functions that are optimal targets. Optimal targets are identified by finding the functions that in combination, yield a high code coverage.
| Func name | Functions filename | Arg count | Args | Function depth | hitcount | instr count | bb count | cyclomatic complexity | Reachable functions | Incoming references | total cyclomatic complexity | Unreached complexity |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
modbus_reply
|
/src/libmodbus/src/modbus.c | 4 | ['struct._modbus *', 'char *', 'int ', 'struct._modbus_mapping_t *'] | 2 | 0 | 1708 | 182 | 57 | 16 | 0 | 132 | 67 |
Implementing fuzzers that target the above functions will improve reachability such that it becomes:
All functions overview
If you implement fuzzers for these functions, the status of all functions in the project will be:
| Func name | Functions filename | Args | Function call depth | Reached by Fuzzers | Fuzzers runtime hit | Func lines hit % | I Count | BB Count | Cyclomatic complexity | Functions reached | Reached by functions | Accumulated cyclomatic complexity | Undiscovered complexity |
|---|
Runtime coverage analysis
This section shows analysis of runtime coverage data.
For futher technical details on how this section is generated, please see the Glossary .
Complex functions with low coverage
| Func name | Function total lines | Lines covered at runtime | percentage covered | Reached by fuzzers |
|---|---|---|---|---|
| _modbus_receive_msg | 114 | 47 | 41.22% | ['FuzzClient'] |
| compute_meta_length_after_function | 32 | 14 | 43.75% | ['FuzzClient'] |
Files and Directories in report
This section shows which files and directories are considered in this report. The main reason for showing this is fuzz introspector may include more code in the reasoning than is desired. This section helps identify if too many files/directories are included, e.g. third party code, which may be irrelevant for the threat model. In the event too much is included, fuzz introspector supports a configuration file that can exclude data from the report. See the following link for more information on how to create a config file: link
Files in report
| Source file | Reached by | Covered by |
|---|---|---|
| [] | [] | |
| /src/libmodbus/fuzz/FuzzServer.c | ['FuzzServer'] | ['FuzzServer'] |
| /src/libmodbus/fuzz/FuzzClient.c | ['FuzzClient'] | ['FuzzClient'] |
| /src/libmodbus/src/modbus-tcp.c | ['FuzzClient', 'FuzzServer'] | ['FuzzServer'] |
| /src/libmodbus/src/modbus.c | ['FuzzClient', 'FuzzServer'] | ['FuzzServer'] |
| /src/libmodbus/src/modbus-data.c | ['FuzzServer'] | ['FuzzServer'] |
Directories in report
| Directory |
|---|
| /src/libmodbus/fuzz/ |
| /src/libmodbus/src/ |
Metadata section
This sections shows the raw data that is used to produce this report. This is mainly used for further processing and developer debugging.
| Fuzzer | Calltree file | Program data file | Coverage file |
|---|---|---|---|
| FuzzClient | fuzzerLogFile-0-J5nMB0l5Aj.data | fuzzerLogFile-0-J5nMB0l5Aj.data.yaml | FuzzClient.covreport |
| FuzzServer | fuzzerLogFile-0-askJQkTeVo.data | fuzzerLogFile-0-askJQkTeVo.data.yaml | FuzzServer.covreport |
Function call coverage
This section shows a chosen list of functions / methods calls and their relative coverage information. By static analysis of the target project code, all of these function call and their caller information, including the source file or class and line number that initiate the call are captured. Column 1 is the function name of that selected functions or methods. Column 2 of each row indicate if the target function covered by any fuzzer calltree information. Column 3 lists all fuzzers (or no fuzzers at all) that have coered that particular function call dynamically. Column 4 shows list of parent function for the specific function call, while column 5 shows possible blocker functions that make the fuzzers fail to reach the specific functions. Both column 4 and 5 will only show information if none of the fuzzers cover the target function calls.
Function in each files in report
| Target sink | Callsite location | Reached by fuzzer | Function call path | Covered by fuzzer | Possible branch blockers |
|---|