CHANGELOG
Version (0.12.1)
2026-01-07 QBDI Team <qbdi@quarkslab.com>
Version (0.12.0)
2025-10-14 QBDI Team <qbdi@quarkslab.com>
Add QBDIPreload implementation for windows (#110, #227 and #277)
Experimental support for IOS AArch64 (#300 and #303). This support is experimental and work only on some jailbroken device.
Add new user API
QBDI::VM::getNbExecBlockandQBDI::VM::reduceCacheToto control the size of QBDI cache (#277)Add new user API
QBDI::VM::getJITInstAnalysisand new analysisQBDI::AnalysisType::ANALYSIS_JITto provide JIT information (#277)Support legacy instruction JCXZ/JECXZ/JRCXZ on X86 and X86_64 (#289)
Add error message when PyQBDI preload fail (#286)
Update to LLVM19 (#271)
Fix missing header (#292)
Fix bugeous initialisation of FTW register on windows (#299)
Fix docs typos (#265)
Update template with new name from 0.11.0 (#259)
Version (0.11.0)
2024-05-17 QBDI Team <qbdi@quarkslab.com>
Fix ARM instrumentation for ‘mov pc, lr’ (#241)
Add switchStackAndCall API (#245)
Rename
QBDI::InstAnalysis::moduleandQBDI::InstAnalysis::symboltoQBDI::InstAnalysis::moduleNameandQBDI::InstAnalysis::symbolName. The same changed applied in C, C++, Python and JS API, but Python and JS API deprecated but still support the previous name.Update LLVM to LLVM17 (#253)
Support copy and pickle for GPRState and FPRState in PyQBDI (#247, #248)
Support python 3.12 (#247)
Version 0.10.0
2023-01-26 QBDI Team <qbdi@quarkslab.com>
Internal update:
Version 0.9.0
2022-03-31 QBDI Team <qbdi@quarkslab.com>
Change internal log system (#174).
The API
QBDI::addLogFilterhas been replaced byQBDI::setLogPriority().The API
QBDI::setLogOutputhas been replaced byQBDI::setLogFile(),QBDI::setLogConsole()andQBDI::setLogDefault().
Fix templates (#186)
Fix Frida-QBDI for Frida 15.0.0 (#192)
Change behavior of
QBDI::VM::addInstrumentedModuleFromAddr()to work with mmap region (#193)Add Priority to InstCallback API (#194). If two or more InstCallback target the same position (PRE or POST) of the same instruction, the priority parameter allows to specify which InstCallback should be called first. see
QBDI::CallbackPrioritySupport for X86
loop,loopeandloopneinstructions (#200)Add support for
FSandGSsegment in X86_64 (#190). To support the feature, the kernel must supportRDFSBASE,RDGSBASE,WRFSBASEandWRGSBASEinstructions (linux >= 5.9). To enable the support, the optionQBDI::Options::OPT_ENABLE_FS_GSmust be enabled.Hide LLVM symbols from shared library and QBDIPreload (#205)
Support python 3.10 for PyQBDI (#206)
Add VMAction
QBDI::VMAction::SKIP_INSTandQBDI::VMAction::SKIP_PATCH(#197)QBDI::VMAction::SKIP_INSTcan be used to emulate the instruction with a PREINST callback. When this VMAction is returned by a PREINST callback, QBDI will directly jump to the POSTINST callback.QBDI::VMAction::SKIP_PATCHcan be used to jump over all the reminding callback for the current instruction. If uses in PREINST position, the instruction will not be executed.
The value associated with the existing
QBDI::VMActionhas changed.Add tutorial for basic block VMEvent (#165)
Support C++ lambda with capture. (#207) see
QBDI::InstCbLambda,QBDI::VMCbLambdaandQBDI::InstrRuleCbLambdaFix a bug where some symbols were missing in QBDIPreload (#209)
Remove new name of libc in QBDIPreload (#211)
Support of some self-modifying code (#212). QBDI will not crash if invalid instructions are found when handling a new basic block.
Add tutorial for ExecBroker VMEvent (#166)
Change
QBDI::getVersion()out parameter to return version to the form0xMMmmpp(#214)
Internal update:
Add static library licenses in LICENSE.txt (#169)
Format code with clang-format and cmake-format (#175)
Fix integer overflow in cache optimisation (#168)
Refactor build system, add llvm build in main cmake with FetchContent, move all LLVM object in a new LLVMCPU class, split internal class, split state by architecture (#178, #179 and #188)
Update LLVM to LLVM 13.0.0, remove zlib dependency (#180, #196)
Remove empty Patch not associated to an MCInst (#195)
Compile assembly with
--noexecstackto have arw-stack when using QBDI on linux (#201)Use build directory to build the documentation (#213)
Use Doxygen 1.9.2 in readthedocs (#214)
Version 0.8.0
2021-02-11 QBDI Team <qbdi@quarkslab.com>
Fix android compilation (#126)
Fix instrumentation of Pusha and Popa on X86 (#127)
Fix getBBMemoryAccess (#128)
Improve the documentation of getBBMemoryAccess
Add recordMemoryAccess callback before any InstCallback
Refactor ExecBlockManager to work with unaligned instruction on X86 and X86-64 (#129)
Drop early support for ARM. The support hasn’t been tested since 0.6.2.
Rework cmake package export to import X86 and X86_64 version of QBDI in one CMake (#146 and #132)
Add
QBDI::VM::getCachedInstAnalysis()to retrieve an InstAnalysis from an address. The address must be cached in the VM. (#148)Change in
InstAnalysisandOperandAnalysis(#153):Add
InstAnalysis.flagsAccessto determine if the instruction uses or sets the flags (EFLAGSregister). The analysisANALYSIS_OPERANDSis needed to use this field.Change
InstAnalysis.mayLoadandInstAnalysis.mayStoredefinition. The field will be true if QBDI detects memory access for the instruction.Add
InstAnalysis.loadSizeandInstAnalysis.storeSize. If the instruction will read or write the memory, the expected size of the access is given by these fields. The analysisANALYSIS_INSTRUCTIONis needed to use this field.Add
InstAnalysis.condition. With the update of LLVM, the mnemonic for conditional jump (likeJE_4) are merged in a unique mnemonicJCC_4. This new field will contain the condition. The analysisANALYSIS_INSTRUCTIONis needed to use this field. A new enumConditionTypehas all the possible value.Add
OPERANDFLAG_IMPLICITforOperandAnalysis.flag. An operand will have this flag when a register is implicit to the instruction.Add
OPERAND_FPRforOperandAnalysis.type. This type is used for floating point registers. For this type,OperandAnalysis.regCtxIdxis the offset inFPRStateor -1 when an offset cannot be provided.Add
OPERAND_SEGforOperandAnalysis.type. This type is used for segments or other unsupported register (likeSSP).Change type of
OperandAnalysis.regCtxIdxto signed integer. When the value is less than 0, the index is invalid.Change algorithm for
OperandAnalysis. The typeOPERAND_INVALIDmay be present in the list of operands when a register is unset with the current instruction. Many operands may describe the used of the same register when a register is used multiple times for different purposes by the instruction.
Add Instrumentation rule callback
QBDI_InstrRuleDataCBKandQBDI::InstrRuleDataCBK(#151)The Instrumentation rule callback receives an InstAnalysis of each instruction during the instrumentation process. Based on this analysis, the callback may insert custom InstCallback for each instruction.
The call order of the callback has changed for the PREINST callback. If an instruction has multiple callbacks in PREINST position, they will be called in the reverse order of registration.
Support SIMD MemoryAccess and change
QBDI::MemoryAccessstructure (#154)Add
QBDI::MemoryAccess::flags. In some cases, QBDI cannot provide all information about the access. This field describes the limitation for each access. Three limitations may be reached:QBDI::MemoryAccessFlags::MEMORY_UNKNOWN_SIZE: the size of the access isn’t known. Only the address is valid. The flag is only set for instruction with REP prefix before the execution of the instruction.QBDI::MemoryAccessFlags::MEMORY_MINIMUM_SIZE: the size isn’t the real size of the access, but the expected minimal size. This flag is used for instruction with complex access likeXSAVEandXRSTOR.QBDI::MemoryAccessFlags::MEMORY_UNKNOWN_VALUE: the value of the access hasn’t been saved. The more common reason is that the access size is greater than the size ofQBDI::MemoryAccess::value. This flag is also used for instruction with REP prefix when the access size cannot be determined during the instrumentation.
Fix MemoryAccess for some generic instruction.
Add VM Options. (#144)
Some options can be provided to the VM to enable or disable some features:
QBDI::Options::OPT_DISABLE_FPR: Disable FPRState backup and restore in context switches. Only the GPRState will be used.QBDI::Options::OPT_DISABLE_OPTIONAL_FPR: WhenQBDI::Options::OPT_DISABLE_FPRisn’t selected, QBDI will detect if a BasicBlock needs FPRState. When BasicBlock doesn’t need FPRState, the state will not be restored. This option forces the restoration and backup of FPRState to every BasicBlock.QBDI::Options::OPT_ATT_SYNTAXfor X86 and X86_64:QBDI::InstAnalysis::disassemblywill be in AT&T syntax instead of Intel Syntax.
Rework documentation (#156)
Internal update:
Reduce LLVM library included in QBDI static library and reduce QBDI package size (#139 and #70)
Use Github Actions to build dev-next package of QBDI (linux, osx and android) and PyQBDI (linux and osx) (#147, #159)
Rewrite frida-qbdi.js and use sphinx-js for frida-QBDI documentation (#146). A version of frida greater or equals to 14.0 is needed to run frida-qbdi.js (need support of ES2019).
Refactor MemoryAccess Code and add new tests (#154)
Handle VMCallback return value (#155)
Optimize Context Switch and FPRState restoration (#144)
Add commit hash in devel version (#158)
Version 0.7.1
2020-02-27 QBDI Team <qbdi@quarkslab.com>
Version 0.7.0
2019-09-10 QBDI Team <qbdi@quarkslab.com>
Add support for the x86 architecture
Add new platforms related to Android: android-X86 and android-X86_64
Improve
MemoryMapstructure by adding the module’s full path if available (#62, #71)Create docker images for QBDI (available on DockerHub qbdi/qbdi) (#56)
Fix and improve operands analysis involved in memory accesses (#58) :
In the previous version, the output of the instruction analysis for some instructions did not contain the information related to memory accesses.
For instance, the operand analysis of
cmp MEM, IMMmisses information about the first operand:cmp dword ptr [rbp + 4 * rbx - 4], 12345678 [0] optype: 1, value : 12345678, size: 8, regOff: 0, regCtxIdx: 0, regName: (null), regaccess : 0This issue has been fixed and the
OperandAnalysisstructure contains a new attribute:flag, which is used to distinctOperandAnalysisinvolved in memory accesses from the others.Here is an example of output:
cmp dword ptr [rbp + 4*rbx - 4], 12345678 [0] optype: 2, flag: 1, value : 48, size: 8, regOff: 0, regCtxIdx: 14, regName: RBP, regaccess : 1 [1] optype: 1, flag: 1, value : 4, size: 8, regOff: 0, regCtxIdx: 0, regName: (null), regaccess : 0 [2] optype: 2, flag: 1, value : 49, size: 8, regOff: 0, regCtxIdx: 1, regName: RBX, regaccess : 1 [3] optype: 1, flag: 1, value : -4, size: 8, regOff: 0, regCtxIdx: 0, regName: (null), regaccess : 0 [4] optype: 1, flag: 0, value : 12345678, size: 4, regOff: 0, regCtxIdx: 0, regName: (null), regaccess : 0 mov rax, qword ptr [rbp - 4] [0] optype: 2, flag: 0, value : 47, size: 8, regOff: 0, regCtxIdx: 0, regName: RAX, regaccess : 2 [1] optype: 2, flag: 1, value : 48, size: 8, regOff: 0, regCtxIdx: 14, regName: RBP, regaccess : 1 [2] optype: 1, flag: 1, value : 1, size: 8, regOff: 0, regCtxIdx: 0, regName: (null), regaccess : 0 [3] optype: 1, flag: 1, value : -4, size: 8, regOff: 0, regCtxIdx: 0, regName: (null), regaccess : 0 mov rax, qword ptr [4*rbx] [0] optype: 2, flag: 0, value : 47, size: 8, regOff: 0, regCtxIdx: 0, regName: RAX, regaccess : 2 [1] optype: 1, flag: 1, value : 4, size: 8, regOff: 0, regCtxIdx: 0, regName: (null), regaccess : 0 [2] optype: 2, flag: 1, value : 49, size: 8, regOff: 0, regCtxIdx: 1, regName: RBX, regaccess : 1 [3] optype: 1, flag: 1, value : 0, size: 8, regOff: 0, regCtxIdx: 0, regName: (null), regaccess : 0 jne -6115 [0] optype: 1, flag: 2, value : -6115, size: 4, regOff: 0, regCtxIdx: 0, regName: (null), regaccess : 0 lea rax, [rbp + 4*rbx - 4] [0] optype: 2, flag: 0, value : 47, size: 8, regOff: 0, regCtxIdx: 0, regName: RAX, regaccess : 2 [1] optype: 2, flag: 4, value : 48, size: 8, regOff: 0, regCtxIdx: 14, regName: RBP, regaccess : 1 [2] optype: 1, flag: 4, value : 4, size: 8, regOff: 0, regCtxIdx: 0, regName: (null), regaccess : 0 [3] optype: 2, flag: 4, value : 49, size: 8, regOff: 0, regCtxIdx: 1, regName: RBX, regaccess : 1 [4] optype: 1, flag: 4, value : -4, size: 8, regOff: 0, regCtxIdx: 0, regName: (null), regaccess : 0
Version 0.6.2
2018-10-19 Cedric TESSIER <ctessier@quarkslab.com>
Version 0.6.1
2018-03-22 Charles HUBAIN <chubain@quarkslab.com>
Fixing a performance regression with the addCodeAddrCB (#42):
Since 0.6, this API would trigger a complete cache flush forcing the engine to regenerate all the instrumented code after each call. Since this API is used inside VM:run(), this had the effect of completely canceling precaching optimization where used.
Fixing support for AVX host without AVX2 support (#19):
Context switching was wrongly using AVX2 instructions instead of AVX instructions causing segfaults under hosts supporting AVX but not AVX2.
Version 0.6
2018-03-02 Charles HUBAIN <chubain@quarkslab.com>
Important performance improvement in the core engine (#30) This slightly changes the behavior of VMEvents.
Fix the addCodeAddrCB API (#37)
atexit and getCurrentProcessMap in python bindings (#35)
Fix getInstAnalysis on BASIC_BLOCK_ENTRY (#28)
Various documentation improvements (#34, #37, #38, #40) and an API uniformisation (#29)
Version 0.5
2017-12-22 Cedric TESSIER <ctessier@quarkslab.com>
Official public release!
Version 0.5 RC3
2017-12-10 Cedric TESSIER <ctessier@quarkslab.com>
Introducing pyqbdi, full featured python bindings based on QBDIPreload library
Revising variadic API to include more friendly prototypes
Various bug, compilation and documentation fixes
Version 0.5 RC2
2017-10-30 Charles HUBAIN <chubain@quarkslab.com>
Apache 2 licensing
New QBDIPreload library for easier dynamic injection under linux and macOS
Various bug, compilation and documentation fixes
Big tree cleanup
Version 0.5 RC1
2017-10-09 Charles HUBAIN <chubain@quarkslab.com>
New Frida bindings
Upgrade to LLVM 5.0
Support for AVX registers
New callback helpers on mnemonics and memory accesses
Basic block precaching API
Automatic cache invalidation when a new instrumentation is added
Instruction and sequence level cache avoids needless retranslation
Upgrade of the validator which now supports Linux and macOS
Version 0.4
2017-01-06 Charles HUBAIN <chubain@quarkslab.com>
Basic Instruction Shadows concept
Memory access PatchDSL statements with support under X86_64 (non SIMD memory access only)
Shadow based memory access API and instrumentation
C and C++ API stabilization
Out-of-tree build and SDK
Overhaul of the entire documentation with a complete PatchDSL explanation and a split between user and developer documentation.
Version 0.3
2016-04-29 Charles HUBAIN <chubain@quarkslab.com>
Partial ARM support, sufficient to run simple program e.g cat, ls, …
Instrumentation filtering system, ExecBroker, allowing the engine to switch between non instrumented and instrumented execution
Complex execution validation system under linux which allows to do instruction per instruction compared execution between a non instrumented and an instrumented instance of a program
New callback system for Engine related event e.g basic block entry / exit, ExecBroker transfer / return.
New (internal) logging system, LogSys, which allows to do priority and tag based filtering of the debug logs.
Version 0.2
2016-01-29 Charles HUBAIN <chubain@quarkslab.com>
Upgrade to LLVM 3.7
Complete X86_64 patching support
Support of Windows X86_64
Basic callback based instrumentation
Usable C++ and C API
User documentation with examples
Uniformisation of PatchDSL
Version 0.1
2015-10-09 Charles HUBAIN <chubain@quarkslab.com>
Ported the PatchDSL from the minijit PoC
Corrected several design flaws in the PatchDSL
Implemented a comparated execution test setup to prove the execution via the JIT yields the same registers and stack state as a normal execution
Basic patching working for ARM and X86_64 architectures as shown by the compared execution tests
Version 0.0
2015-09-17 Charles HUBAIN <chubain@quarkslab.com>
Working dependency system for LLVM and Google Test
ExecBlock working and tested on linux-X86_64, linux-ARM, android-ARM and macOS-X86_64
Deployed buildbot infrastructure for automated build and test on linux-X86_64 and linux-ARM