rustsec-2026-0080
Vulnerability from osv_rustsec
Published
2026-01-19 12:00
Modified
2026-04-02 12:03
Summary
Multiple soundness issues in `scaly` safe APIs
Details
Affected versions contain multiple safe APIs that can trigger undefined behavior:
Array<T>::indexcan perform an out-of-bounds read.String::get_lengthcan perform an out-of-bounds read.String::append_charactercan perform an invalid write.String::to_c_stringcan perform an out-of-bounds write.
These issues were reproduced against scaly 0.0.37 under Miri. And the crate is unmaintained.
References
| URL | Type | |
|---|---|---|
{
"affected": [
{
"database_specific": {
"categories": [],
"cvss": null,
"informational": "unsound"
},
"ecosystem_specific": {
"affected_functions": null,
"affects": {
"arch": [],
"functions": [],
"os": []
}
},
"package": {
"ecosystem": "crates.io",
"name": "scaly",
"purl": "pkg:cargo/scaly"
},
"ranges": [
{
"events": [
{
"introduced": "0.0.0-0"
}
],
"type": "SEMVER"
}
],
"versions": []
}
],
"aliases": [],
"database_specific": {
"license": "CC0-1.0"
},
"details": "Affected versions contain multiple safe APIs that can trigger undefined\nbehavior:\n\n- `Array\u003cT\u003e::index` can perform an out-of-bounds read.\n- `String::get_length` can perform an out-of-bounds read.\n- `String::append_character` can perform an invalid write.\n- `String::to_c_string` can perform an out-of-bounds write.\n\nThese issues were reproduced against `scaly` 0.0.37 under Miri. And the crate is unmaintained.",
"id": "RUSTSEC-2026-0080",
"modified": "2026-04-02T12:03:57Z",
"published": "2026-01-19T12:00:00Z",
"references": [
{
"type": "PACKAGE",
"url": "https://crates.io/crates/scaly"
},
{
"type": "ADVISORY",
"url": "https://rustsec.org/advisories/RUSTSEC-2026-0080.html"
},
{
"type": "REPORT",
"url": "https://github.com/rustsec/advisory-db/issues/2594"
}
],
"related": [],
"severity": [],
"summary": "Multiple soundness issues in `scaly` safe APIs"
}
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…