CCured: type-safe retrofitting of legacy software

438 citations recorded by the source corpus.

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

CETS: compiler enforced temporal safety for C (2010, methodology): “Although use of fat pointers has been proposed in variety of contexts [5, 19, 23, 30], fat pointers have the drawback of changing memory layout in programmer-visible ways, and the modiﬁed memory layout makes interfacing with libraries challenging [10, 23].”
Preventing Memory Error Exploits with WIT (2008, background): “For example, CCured [33] reports a maximum overhead of 87% and an average of 28% for Olden benchmarks, but it slows down some applications by more than a factor of 9.”
Securing software by enforcing data-flow integrity (2006, background): “CCured [30] and Cyclone [24] propose memorysafe dialects of C that prevent all these attacks.”
Baggy Bounds Checking: An Efficient and Backwards-Compatible Defense against Out-of-Bounds Errors (2009, methodology): “Initial attempts incurred a signiﬁcant overhead [19, 30, 36] (typically 2x–10x) be-Object”