Skip to content

Remaining Technical Debt #78

@AndrewQuijano

Description

@AndrewQuijano

Feature

  • New Language supported
  • Bug improvements
  • Technical Debt remediation/Workflow improvement
  • Binding support for: language
  • Other (elaborated below)

Describe the feature you'd like
Let's update LAVA to be easier to maintain, and also start upgrading it.

Additional context
I want to complete the following tasks next PR:

1- Create a wheel file for PyPi, see #79 and see #86

2- Update from LLVM-11 to LLVM-14 to match PANDA. This makes LAVA Ubuntu 24 friendly too, see #80. Given the LLVM upgrade we can remove OMG, see #83

3- PANDA should support a folder of inputs for testing instead of specific files. This is a CRITICAL bug to fix for research purposes. See #82

4- FBI needs to be rewritten in Python. See #84

5- Swap for all Python instead of Bash. See #90

6- Utilize Protobuf to enforce consistency for both C++/Python to avoid database issues. See #87

7- Automate the pre-processing step, See #91

8- LAVA should be assuming the binaries are installed, see #88

9- Use PANDA hypercall struct from PANDA, avoiding code duplication see #92

10- Deprecate BTrace and use compiledb instead see #93

Note:
About finding the LAVA code with vulnerable code, you have to check the branches.

Image

You can confirm this by seeing that the top has some macros. If you see the top, it seems to be missing some macros. But this is because ArgDataflow is false.

Plus given there are crashes, this does seem to work as expected.

Image

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions