Vulnerability CriticalRUSTSEC-2019-0028 · flatbuffers
RUSTSEC-2019-0028: Unsound `impl Follow for bool`
Short answerA security vulnerability in the flatbuffers crate: Unsound `impl Follow for bool`. Critical severity (CVSS 9.8). Fixed in 0.6.1: update to a fixed version.
| Crate | flatbuffers |
|---|---|
| Type | Vulnerability |
| Affected versions | From 0.4.0 before 0.6.1. |
| Fixed in | 0.6.1 |
| Severity | Critical, CVSS 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| Published | 2019-10-20 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2019-25004, GHSA-gx73-2498-r55c |
| Affected functions | flatbuffers::Follow::follow |
What to do
- See which version you have:
cargo tree -i flatbuffers(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p flatbuffers. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for exampleflatbuffers = "0.6.1") or update the dependency that pulls it in. - Check again with
cargo audit, or paste your Cargo.lock into our Cargo.toml checker.
Details from the advisory
The implementation of impl Follow for bool allows to reinterpret arbitrary bytes as a bool.
In Rust bool has stringent requirements for its in-memory representation. Use of this function allows to violate these requirements and invoke undefined behaviour in safe code.
References
- Package: crates.io/crates/flatbuffers
- Advisory: rustsec.org/advisories/RUSTSEC-2019-0028.html
- Report: github.com/google/flatbuffers/issues/5530
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Other advisories for flatbuffers
Up next
Same crateflatbuffers: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?