NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🦀
🦀 crates.io
Not in CISA KEV
CRITICAL severity

Generated code can read and write out of bounds in safe codeGHSA-3jch-9qgp-4844

CRITICALFix: google/flatbuffers#7518

GHSA-3jch-9qgp-4844 is a critical-severity (CVSS 9.8) vulnerability in flatbuffers. A fix is available for flatbuffers — see the affected versions and patch details below.

Also known asRUSTSEC-2021-0122
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 8, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🦀flatbuffers

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🦀crates.ioflatbuffersall versions22.9.29cargo update -p flatbuffers --precise 22.9.29

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for flatbuffers, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update flatbuffers to 22.9.29 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3jch-9qgp-4844 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-3jch-9qgp-4844 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works
Generated code can read and write out of bounds in safe…