GHSA-2226-4V3C-CFF8
Vulnerability from github – Published: 2022-06-17 00:18 – Updated: 2022-06-17 00:18
VLAI?
Summary
Stack overflow in rustc_serialize when parsing deeply nested JSON
Details
When parsing JSON using json::Json::from_str, there is no limit to the depth of the stack, therefore deeply nested objects can cause a stack overflow, which aborts the process.
Example code that triggers the vulnerability is
fn main() {
let _ = rustc_serialize::json::Json::from_str(&"[0,[".repeat(10000));
}
serde is recommended as a replacement to rustc_serialize.
{
"affected": [
{
"package": {
"ecosystem": "crates.io",
"name": "rustc-serialize"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "0.3.24"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [],
"database_specific": {
"cwe_ids": [],
"github_reviewed": true,
"github_reviewed_at": "2022-06-17T00:18:24Z",
"nvd_published_at": null,
"severity": "MODERATE"
},
"details": "When parsing JSON using `json::Json::from_str`, there is no limit to the depth of the stack, therefore deeply nested objects can cause a stack overflow, which aborts the process.\n\nExample code that triggers the vulnerability is\n\n```rust\nfn main() {\n let _ = rustc_serialize::json::Json::from_str(\u0026\"[0,[\".repeat(10000));\n}\n```\n\n[serde](https://crates.io/crates/serde) is recommended as a replacement to rustc_serialize.\n",
"id": "GHSA-2226-4v3c-cff8",
"modified": "2022-06-17T00:18:24Z",
"published": "2022-06-17T00:18:24Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/rust-lang-deprecated/rustc-serialize"
},
{
"type": "PACKAGE",
"url": "https://github.com/rust-lang/rustc-serialize"
},
{
"type": "WEB",
"url": "https://rustsec.org/advisories/RUSTSEC-2022-0004.html"
}
],
"schema_version": "1.4.0",
"severity": [],
"summary": "Stack overflow in rustc_serialize when parsing deeply nested JSON"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…