alive2
klee
Our great sponsors
alive2 | klee | |
---|---|---|
4 | 4 | |
675 | 2,454 | |
3.7% | 1.6% | |
9.3 | 8.8 | |
2 days ago | 7 days ago | |
C++ | C++ | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
alive2
-
Basic SAT model of x86 instructions using Z3, autogenerated from Intel docs
You can use it to (mostly) validate small snippets are the same. See Alive2 for the application of Z3/formalization of programs as SMT for that [1]. As far as I'm aware there are some problems scaling up to arbitrarily sized programs due to a lack of formalization in higher level languages in addition to computational constraints. With a lot of time and effort it can be done though [2].
1. https://github.com/AliveToolkit/alive2
2. https://sel4.systems/
- John Regehr: Alive2 LLVM optims verification
-
Verifying GCC optimizations using an SMT solver
Yeah, this kind of thing is nice.
Alive had been used for years (almost a decade actually) by people to verify LLVM instcombine transforms.
Alive2 (https://github.com/AliveToolkit/alive2) makes it easier to do the same with most optimization passes.
-
Programming in Z3 by learning to think like a compiler
Alive/Alive2 [1] is one of the most famous frameworks for compiler transformation verification using BitVec logic
[1] https://github.com/AliveToolkit/alive2
klee
- GrayC: Greybox Fuzzing of Compilers and Analysers for C [pdf]
-
Go Noob question: How can I output LLVM IR, instrument it and also looking for a symbolic execution engine
I also want to use something like KLEE: https://klee.github.io/
-
If people make game engines in C, why do (other) people say C is impossibly hard and can never be correct?
I think that KLEE was quite good at that. See https://klee.github.io/
-
A Saudi woman's iPhone revealed hacking around the world
I think the most critical part the flow is the integer overflow bug, and it is totally avoidable. I am a software engine at Microsoft. Half my time was spent on security and compliance. We have the right tool, right policy to avoid such things happen. However, I'm not saying Microsoft software is free of integer overflow bugs. I don't intend to advertise Microsoft C/C++ development tools here, but they are what I know most.
Let's go to the technical part: If you are asked to implement the binary algorithm with your favorite programming language, how do you verify your code is correct? Unit-tests. How many test cases you may need? More than 10. As long as you have enough tests, your don't need to worry too much. But how much test coverage is enough? Please remember JDK had a integer overflow bug in their binary search in early 2000s. So, people know the algorithm, but normally people don't know how to test their code, therefore most people can't write bug-free binary search code. And any non-trivial C/C++ function may need tens of thousands test cases. Simply you can't write the tests by hand.
You need the right tools: fuzzing and static analysis.
At Microsoft, every file parser should go through fuzzing, which basically is you generate some random input, then you run your tests with the random inputs. Not very fantastic. But there is another kind of fuzzing: symbolic execution, which tries to find all the possible execution paths of your code. If you run symbolic execution with your binary search code, you can get 100% test coverage. And it is guaranteed bug-free. It is like a math proof. Please note the advantage is based on human just had surprising great advancement on SAT solvers in the last 20 years. And often you need to make some compromises between your business goal and security. Most functions can't reach 100% test coverage. You need to simplify them. See https://github.com/klee/klee to get a quickstart. Though C/C++ is often considered unsafe, they have the best fuzzer.
Then it is about SAL annotation and static analyzer. In C, whenever you pass a pointer of an array to another function, you should also pass its length with it. And in the callee function you should check the length. If you forgot it, your static code analyzer will give you a warning. In such a sense, if you didn't allocate enough memory, it will only result an error code being returned instead of undefined behavior.
The last thing: Use safeint wrapping your malloc function. https://docs.microsoft.com/en-us/cpp/safeint/safeint-library...
When we move off the binary search toy example to a real code base, clearly you can see how much extra effort is needed to make the code safe. Please pardon me, most OSS libraries don't have the resource. Many famous OSS projects are "Mom-and-pop" shops. They don't have any compliance rule. They invest very little on fuzzing. So the big companies really should help them. Now you see an integer overflow bug was found in Apple's image render, but was the code written by Apple? Not necessarily. Now we all see the importance of the Open Source movement. It's time to think how to harden their security. For example, even I want to spend my free time on adding SAL annotations to an OSS project I love, would the maintainers accept it?
What are some alternatives?
CrossHair - An analysis tool for Python that blurs the line between testing and type systems.
Triton - Triton is a dynamic binary analysis library. Build your own program analysis tools, automate your reverse engineering, perform software verification or just emulate code.
recreational-rosette - Some fun examples of solving problems with symbolic execution
zz - 🍺🐙 ZetZ a zymbolic verifier and tranzpiler to bare metal C
bap - Binary Analysis Platform
Symbolica - Symbolica's open-source symbolic execution engine. [Moved to: https://github.com/Symbolica/Symbolica]
rust-verification-tools - RVT is a collection of tools/libraries to support both static and dynamic verification of Rust programs.
llvm-tutor - A collection of out-of-tree LLVM passes for teaching and learning
I.Ming - I.Ming ( I.明體 / 一点明朝体 / 一點明體 )
Cassius - A CSS specification and reasoning engine
iansui - 芫荽,基於 Klee One 改造的學習用台灣繁體字型