clamav

Commit Graph

Author	SHA1	Message	Date
Török Edvin	daad92ace3	Relax bounds checks. It was rejecting correct code. Bounds checks were too strict, causing the bytecode to abort when it shouldn't. This happened when trying to access the last byte of an array, the verifier was too conservative and considered to be out of bounds, when in fact it wasn't. This is an update of the runtime verifier from the bytecode compiler.	16 years ago
Török Edvin	2f995d9abc	Fix load of multiple unsigned bytecodes (bb #1924 ) All bytecode functions are loaded in a single module, the bounds verifier is run, and then stack protectors are inserted. The problem is that when the next bytecode function is loaded, all functions get run through the verifier again (including those which got the stack protector applied), and the bounds verifier rejects it (it doesn't know about stack protectors). The fix is to skip running the bounds verifier when a function already has the stack protector applied, when run in libclamav. This affects only loading of multiple unsigned bytecodes, or an unsigned bytecode + bytecode.cvd. Load of a single unsigned bytecode works, and load of multiple signed bytecodes is not affected (since the verifier is skipped there).	16 years ago
Török Edvin	556eaf0442	Update ClamBCRTChecks.cpp from bytecode compiler: Check bounds of each pointer passed to/from APIcalls, forbid recursion.	16 years ago
Török Edvin	b56bea54d3	New API for buffer fill.	16 years ago
Török Edvin	aa745db74d	Add clamscan commandline to load bytecode in debug mode.	16 years ago
Török Edvin	dcd3e8019b	nullcheck.	16 years ago
Török Edvin	a45651d4cb	add another missing file	16 years ago

7 Commits (a3a6b8138d98f20bd1e6dc9924da0f7193def205)