Memory safety¶
Projects, T. C. Memory safety.
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Domain-specific¶
- Pointer
- … similar shares for its own projects (about 70% of Chromium's high- and critical-severity security bugs; 76% of Android's vulnerabilities in 2019) — totals that count out-of-bounds (spatial) errors as well as the use-after-free errors of the pointer-outlives-referent family, which are about half of Chromium's share
This sourceChromium Security, n.d. Around 70% of Chromium's serious security bugs are memory-safety problems and half of those are use-after-free bugs, in an analysis of 912 high or critical severity security bugs since 2015.
- … similar shares for its own projects (about 70% of Chromium's high- and critical-severity security bugs; 76% of Android's vulnerabilities in 2019) — totals that count out-of-bounds (spatial) errors as well as the use-after-free errors of the pointer-outlives-referent family, which are about half of Chromium's share
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Not recorded. The single citation of this work carries no recorded support check.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:933ffc344432 · see in the full table