Project overview: pyparsing
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 | Runtime reached by Fuzzers | Combined 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: fuzz_parse
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 project has no code coverage. Will not display blockers as blockers depend on code coverage.
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
pyparsing.core.ParserElement.run_tests
|
pyparsing.core | 15 | ['N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A'] | 12 | 0 | 17 | 13 | 8 | 217 | 1 | 695 | 484 |
pyparsing.diagram.to_railroad
|
pyparsing.diagram | 6 | ['N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A'] | 12 | 0 | 5 | 5 | 5 | 190 | 1 | 626 | 117 |
pyparsing.helpers.one_of
|
pyparsing.helpers | 5 | ['N/A', 'N/A', 'N/A', 'N/A', 'N/A'] | 12 | 0 | 6 | 11 | 7 | 193 | 1 | 614 | 55 |
pyparsing.testing.pyparsing_test.reset_pyparsing_context.restore
|
pyparsing.testing | 1 | ['N/A'] | 4 | 0 | 4 | 2 | 4 | 26 | 1 | 84 | 54 |
pyparsing.helpers._makeTags
|
pyparsing.helpers | 4 | ['N/A', 'N/A', 'N/A', 'N/A'] | 9 | 0 | 3 | 2 | 4 | 112 | 4 | 349 | 53 |
pyparsing.core.Each.parseImpl
|
pyparsing.core | 4 | ['N/A', 'N/A', 'N/A', 'N/A'] | 4 | 0 | 10 | 8 | 6 | 23 | 0 | 78 | 42 |
pyparsing.results.ParseResults.dump
|
pyparsing.results | 5 | ['N/A', 'N/A', 'N/A', 'N/A', 'N/A'] | 4 | 0 | 9 | 7 | 6 | 19 | 1 | 66 | 39 |
pyparsing.core.Word.__init__
|
pyparsing.core | 9 | ['N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A'] | 3 | 0 | 1 | 20 | 11 | 21 | 0 | 76 | 37 |
pyparsing.core.IndentedBlock.parseImpl
|
pyparsing.core | 4 | ['N/A', 'N/A', 'N/A', 'N/A'] | 11 | 0 | 3 | 2 | 4 | 168 | 0 | 534 | 36 |
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 | Runtime reached by Fuzzers | Combined 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 |
|---|
Fuzz engine guidance
This sections provides heuristics that can be used as input to a fuzz engine when running a given fuzz target. The current focus is on providing input that is usable by libFuzzer.
/src/fuzz_parse.py
Dictionary
Use this with the libFuzzer -dict=DICT.file flag
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 |
|---|---|---|
| [] | [] | |
| itertools | [] | [] |
| difflib | [] | [] |
| importlib | [] | [] |
| argparse | [] | [] |
| atheris | [] | [] |
| pyparsing.ai.show_best_practices | [] | [] |
| datetime | [] | [] |
| pyparsing.tools | [] | [] |
| abc | [] | [] |
|
|
[] | [] |
| pyparsing.unicode | [] | [] |
| pyparsing.results | [] | [] |
| threading | [] | [] |
| pyparsing.testing | [] | [] |
| pyparsing.ai | [] | [] |
| inspect | [] | [] |
| sys | [] | [] |
| pyparsing.helpers | ['fuzz_parse'] | [] |
| unittest | [] | [] |
| operator | [] | [] |
| ...fuzz_parse | ['fuzz_parse'] | [] |
| pyparsing.tools.cvt_pyparsing_pep8_names | ['fuzz_parse'] | [] |
| pyparsing.actions | [] | [] |
| collections | [] | [] |
| pyparsing.core | ['fuzz_parse'] | [] |
| traceback | [] | [] |
| warnings | [] | [] |
| pyparsing.util | ['fuzz_parse'] | [] |
| contextlib | [] | [] |
| pyparsing.ai.show_best_practices.__main__ | [] | [] |
| typing | [] | [] |
| jinja2 | [] | [] |
| pathlib | [] | [] |
| pyparsing.diagram | [] | [] |
| io | [] | [] |
| railroad | [] | [] |
| functools | [] | [] |
| pyparsing | [] | [] |
| pyparsing.exceptions | [] | [] |
| re | [] | [] |
| os | [] | [] |
| pyparsing.common | [] | [] |
| types | [] | [] |
Directories in report
| Directory |
|---|