Vulnerability HighRUSTSEC-2019-0003 · protobuf
RUSTSEC-2019-0003: Out of Memory in stream::read_raw_bytes_into()
Short answerA security vulnerability in the protobuf crate: Out of Memory in stream::read_raw_bytes_into(). High severity (CVSS 7.5). Fixed in 1.7.5, 2.6.0: update to a fixed version.
| Crate | protobuf |
|---|---|
| Type | Vulnerability (denial-of-service) |
| Affected versions | Before 1.7.5; from 2.0.0 before 2.6.0. |
| Fixed in | 1.7.5, 2.6.0 |
| Severity | High, CVSS 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| Published | 2019-06-08 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2019-15544, GHSA-mh6h-f25p-98f8 |
| Affected functions | protobuf::stream::read_raw_bytes_into |
What to do
- See which version you have:
cargo tree -i protobuf(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p protobuf. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for exampleprotobuf = "2.6.0") 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
Affected versions of this crate called Vec::reserve() on user-supplied input.
This allows an attacker to cause an Out of Memory condition while calling the vulnerable method on untrusted data.
References
- Package: crates.io/crates/protobuf
- Advisory: rustsec.org/advisories/RUSTSEC-2019-0003.html
- Report: github.com/stepancheg/rust-protobuf/issues/411
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 protobuf
Up next
Same crateprotobuf: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?