Generated code can read and write out of bounds in safe code
Priority LOW 38Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
Code generated by flatbuffers' compiler is `unsafe` but not marked as such. See https://github.com/google/flatbuffers/issues/6627 for details. All users that use generated code by `flatbuffers` compiler are recommended to: 1. not expose flatbuffer generated code as part of their public APIs 2. audit their code and look for any usage of `follow`, `push`, or any method that uses them (e.g. `self_follow`). 3. Carefuly go through the crates' documentation to understand which "safe" APIs are not intended to be used.
Why it matters now
Fix Fixed flatbuffers (crates.io): 22.9.29
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | flatbuffers (crates.io) | before 22.9.29 | 22.9.29 | Patch available | GHSA-3jch-9qgp-4844 |
- flatbuffers (crates.io) Vendor— Affected before 22.9.29 Fixed in 22.9.29 Patch available GHSA-3jch-9qgp-4844
Remediation
- Fix · GHSA-3jch-9qgp-4844 flatbuffers (crates.io) Fixed in 22.9.29 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-3jch-9qgp-4844
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences