anstream
Activity
- Latest release
- 7mo ago
- Total releases
- 32
- Cadence
- ~9 days
- Last 12 months
- 2
Details
- License
- MIT OR Apache-2.0
- First release
- Mar 16, 2023
| Version | Released | |
|---|---|---|
1.0.0
unknown
|
1.0.0
unknown
Dependencies (12)
+ 4 more |
|
0.6.21
unknown
|
0.6.21
unknown
Dependencies (12)
+ 4 more |
|
0.6.20
unknown
|
0.6.20
unknown
Dependencies (12)
+ 4 more |
|
0.6.19
unknown
|
0.6.19
unknown
Dependencies (12)
+ 4 more |
|
0.6.18
unknown
|
0.6.18
unknown
Dependencies (12)
+ 4 more |
|
0.6.17
unknown
|
0.6.17
unknown
Dependencies (12)
+ 4 more |
|
0.6.16
unknown
|
0.6.16
unknown
Dependencies (12)
+ 4 more |
|
0.6.15
unknown
|
0.6.15
unknown
Dependencies (12)
+ 4 more |
|
0.6.14
unknown
|
0.6.14
unknown
Dependencies (12)
+ 4 more |
|
0.6.13
unknown
|
0.6.13
unknown
Dependencies (11)
+ 3 more |
|
0.6.12
unknown
|
0.6.12
unknown
Dependencies (11)
+ 3 more |
|
0.6.11
unknown
|
0.6.11
unknown
Dependencies (11)
+ 3 more |
|
0.6.10
unknown
|
0.6.10
unknown
Dependencies (11)
+ 3 more |
|
0.6.9
unknown
|
0.6.9
unknown
Dependencies (11)
+ 3 more |
|
0.6.8
unknown
|
0.6.8
unknown
Dependencies (11)
+ 3 more |
|
0.6.7
unknown
1 CVE
GHSA-2rxc-gjrp-vjhx
RUSTSEC-2024-0404
Dec 04, 2024
Unsoundness in anstream
Medium
When given a valid UTF8 string "ö\x1b😀", the function in crates/anstream/src/adapter/strip.rs will be confused. The UTF8 bytes are \xc3\xb6 then \x1b then \xf0\x9f\x98\x80. When looping over "non-printable bytes" \x1b\xf0 will be considered as some non-printable sequence. This will produce a broken str from the incorrectly segmented bytes via str::from_utf8_unchecked, and that should never happen. Full credit goes to @Ralith who reviewed this code and asked @burakemir to follow up. Fixed in
0.6.8
References Updated Sep 10, 2026 · Source: OSV.dev |
0.6.7
unknown
Dependencies (11)
+ 3 more |
|
0.6.6
unknown
1 CVE
GHSA-2rxc-gjrp-vjhx
RUSTSEC-2024-0404
Dec 04, 2024
Unsoundness in anstream
Medium
When given a valid UTF8 string "ö\x1b😀", the function in crates/anstream/src/adapter/strip.rs will be confused. The UTF8 bytes are \xc3\xb6 then \x1b then \xf0\x9f\x98\x80. When looping over "non-printable bytes" \x1b\xf0 will be considered as some non-printable sequence. This will produce a broken str from the incorrectly segmented bytes via str::from_utf8_unchecked, and that should never happen. Full credit goes to @Ralith who reviewed this code and asked @burakemir to follow up. Fixed in
0.6.8
References Updated Sep 10, 2026 · Source: OSV.dev |
0.6.6
unknown
Dependencies (11)
+ 3 more |
|
0.6.5
unknown
1 CVE
GHSA-2rxc-gjrp-vjhx
RUSTSEC-2024-0404
Dec 04, 2024
Unsoundness in anstream
Medium
When given a valid UTF8 string "ö\x1b😀", the function in crates/anstream/src/adapter/strip.rs will be confused. The UTF8 bytes are \xc3\xb6 then \x1b then \xf0\x9f\x98\x80. When looping over "non-printable bytes" \x1b\xf0 will be considered as some non-printable sequence. This will produce a broken str from the incorrectly segmented bytes via str::from_utf8_unchecked, and that should never happen. Full credit goes to @Ralith who reviewed this code and asked @burakemir to follow up. Fixed in
0.6.8
References Updated Sep 10, 2026 · Source: OSV.dev |
0.6.5
unknown
Dependencies (11)
+ 3 more |
|
0.6.4
unknown
1 CVE
GHSA-2rxc-gjrp-vjhx
RUSTSEC-2024-0404
Dec 04, 2024
Unsoundness in anstream
Medium
When given a valid UTF8 string "ö\x1b😀", the function in crates/anstream/src/adapter/strip.rs will be confused. The UTF8 bytes are \xc3\xb6 then \x1b then \xf0\x9f\x98\x80. When looping over "non-printable bytes" \x1b\xf0 will be considered as some non-printable sequence. This will produce a broken str from the incorrectly segmented bytes via str::from_utf8_unchecked, and that should never happen. Full credit goes to @Ralith who reviewed this code and asked @burakemir to follow up. Fixed in
0.6.8
References Updated Sep 10, 2026 · Source: OSV.dev |
0.6.4
unknown
Dependencies (10)
+ 2 more |
|
0.6.3
unknown
1 CVE
GHSA-2rxc-gjrp-vjhx
RUSTSEC-2024-0404
Dec 04, 2024
Unsoundness in anstream
Medium
When given a valid UTF8 string "ö\x1b😀", the function in crates/anstream/src/adapter/strip.rs will be confused. The UTF8 bytes are \xc3\xb6 then \x1b then \xf0\x9f\x98\x80. When looping over "non-printable bytes" \x1b\xf0 will be considered as some non-printable sequence. This will produce a broken str from the incorrectly segmented bytes via str::from_utf8_unchecked, and that should never happen. Full credit goes to @Ralith who reviewed this code and asked @burakemir to follow up. Fixed in
0.6.8
References Updated Sep 10, 2026 · Source: OSV.dev |
0.6.3
unknown
Dependencies (10)
+ 2 more |
|
0.6.2
unknown
1 CVE
GHSA-2rxc-gjrp-vjhx
RUSTSEC-2024-0404
Dec 04, 2024
Unsoundness in anstream
Medium
When given a valid UTF8 string "ö\x1b😀", the function in crates/anstream/src/adapter/strip.rs will be confused. The UTF8 bytes are \xc3\xb6 then \x1b then \xf0\x9f\x98\x80. When looping over "non-printable bytes" \x1b\xf0 will be considered as some non-printable sequence. This will produce a broken str from the incorrectly segmented bytes via str::from_utf8_unchecked, and that should never happen. Full credit goes to @Ralith who reviewed this code and asked @burakemir to follow up. Fixed in
0.6.8
References Updated Sep 10, 2026 · Source: OSV.dev |
0.6.2
unknown
Dependencies (10)
+ 2 more |
|
0.6.1
unknown
1 CVE
GHSA-2rxc-gjrp-vjhx
RUSTSEC-2024-0404
Dec 04, 2024
Unsoundness in anstream
Medium
When given a valid UTF8 string "ö\x1b😀", the function in crates/anstream/src/adapter/strip.rs will be confused. The UTF8 bytes are \xc3\xb6 then \x1b then \xf0\x9f\x98\x80. When looping over "non-printable bytes" \x1b\xf0 will be considered as some non-printable sequence. This will produce a broken str from the incorrectly segmented bytes via str::from_utf8_unchecked, and that should never happen. Full credit goes to @Ralith who reviewed this code and asked @burakemir to follow up. Fixed in
0.6.8
References Updated Sep 10, 2026 · Source: OSV.dev |
0.6.1
unknown
Dependencies (10)
+ 2 more |
|
0.6.0
unknown
1 CVE
GHSA-2rxc-gjrp-vjhx
RUSTSEC-2024-0404
Dec 04, 2024
Unsoundness in anstream
Medium
When given a valid UTF8 string "ö\x1b😀", the function in crates/anstream/src/adapter/strip.rs will be confused. The UTF8 bytes are \xc3\xb6 then \x1b then \xf0\x9f\x98\x80. When looping over "non-printable bytes" \x1b\xf0 will be considered as some non-printable sequence. This will produce a broken str from the incorrectly segmented bytes via str::from_utf8_unchecked, and that should never happen. Full credit goes to @Ralith who reviewed this code and asked @burakemir to follow up. Fixed in
0.6.8
References Updated Sep 10, 2026 · Source: OSV.dev |
0.6.0
unknown
Dependencies (10)
+ 2 more |
|
0.5.0
unknown
1 CVE
GHSA-2rxc-gjrp-vjhx
RUSTSEC-2024-0404
Dec 04, 2024
Unsoundness in anstream
Medium
When given a valid UTF8 string "ö\x1b😀", the function in crates/anstream/src/adapter/strip.rs will be confused. The UTF8 bytes are \xc3\xb6 then \x1b then \xf0\x9f\x98\x80. When looping over "non-printable bytes" \x1b\xf0 will be considered as some non-printable sequence. This will produce a broken str from the incorrectly segmented bytes via str::from_utf8_unchecked, and that should never happen. Full credit goes to @Ralith who reviewed this code and asked @burakemir to follow up. Fixed in
0.6.8
References Updated Sep 10, 2026 · Source: OSV.dev |
0.5.0
unknown
Dependencies (10)
+ 2 more |
|
0.4.0
unknown
1 CVE
GHSA-2rxc-gjrp-vjhx
RUSTSEC-2024-0404
Dec 04, 2024
Unsoundness in anstream
Medium
When given a valid UTF8 string "ö\x1b😀", the function in crates/anstream/src/adapter/strip.rs will be confused. The UTF8 bytes are \xc3\xb6 then \x1b then \xf0\x9f\x98\x80. When looping over "non-printable bytes" \x1b\xf0 will be considered as some non-printable sequence. This will produce a broken str from the incorrectly segmented bytes via str::from_utf8_unchecked, and that should never happen. Full credit goes to @Ralith who reviewed this code and asked @burakemir to follow up. Fixed in
0.6.8
References Updated Sep 10, 2026 · Source: OSV.dev |
0.4.0
unknown
Dependencies (11)
+ 3 more |
|
0.3.2
unknown
1 CVE
GHSA-2rxc-gjrp-vjhx
RUSTSEC-2024-0404
Dec 04, 2024
Unsoundness in anstream
Medium
When given a valid UTF8 string "ö\x1b😀", the function in crates/anstream/src/adapter/strip.rs will be confused. The UTF8 bytes are \xc3\xb6 then \x1b then \xf0\x9f\x98\x80. When looping over "non-printable bytes" \x1b\xf0 will be considered as some non-printable sequence. This will produce a broken str from the incorrectly segmented bytes via str::from_utf8_unchecked, and that should never happen. Full credit goes to @Ralith who reviewed this code and asked @burakemir to follow up. Fixed in
0.6.8
References Updated Sep 10, 2026 · Source: OSV.dev |
0.3.2
unknown
Dependencies (11)
+ 3 more |
|
0.3.1
unknown
1 CVE
GHSA-2rxc-gjrp-vjhx
RUSTSEC-2024-0404
Dec 04, 2024
Unsoundness in anstream
Medium
When given a valid UTF8 string "ö\x1b😀", the function in crates/anstream/src/adapter/strip.rs will be confused. The UTF8 bytes are \xc3\xb6 then \x1b then \xf0\x9f\x98\x80. When looping over "non-printable bytes" \x1b\xf0 will be considered as some non-printable sequence. This will produce a broken str from the incorrectly segmented bytes via str::from_utf8_unchecked, and that should never happen. Full credit goes to @Ralith who reviewed this code and asked @burakemir to follow up. Fixed in
0.6.8
References Updated Sep 10, 2026 · Source: OSV.dev |
0.3.1
unknown
Dependencies (11)
+ 3 more |
|
0.3.0
unknown
1 CVE
GHSA-2rxc-gjrp-vjhx
RUSTSEC-2024-0404
Dec 04, 2024
Unsoundness in anstream
Medium
When given a valid UTF8 string "ö\x1b😀", the function in crates/anstream/src/adapter/strip.rs will be confused. The UTF8 bytes are \xc3\xb6 then \x1b then \xf0\x9f\x98\x80. When looping over "non-printable bytes" \x1b\xf0 will be considered as some non-printable sequence. This will produce a broken str from the incorrectly segmented bytes via str::from_utf8_unchecked, and that should never happen. Full credit goes to @Ralith who reviewed this code and asked @burakemir to follow up. Fixed in
0.6.8
References Updated Sep 10, 2026 · Source: OSV.dev |
0.3.0
unknown
Dependencies (11)
+ 3 more |
|
0.2.6
unknown
1 CVE
GHSA-2rxc-gjrp-vjhx
RUSTSEC-2024-0404
Dec 04, 2024
Unsoundness in anstream
Medium
When given a valid UTF8 string "ö\x1b😀", the function in crates/anstream/src/adapter/strip.rs will be confused. The UTF8 bytes are \xc3\xb6 then \x1b then \xf0\x9f\x98\x80. When looping over "non-printable bytes" \x1b\xf0 will be considered as some non-printable sequence. This will produce a broken str from the incorrectly segmented bytes via str::from_utf8_unchecked, and that should never happen. Full credit goes to @Ralith who reviewed this code and asked @burakemir to follow up. Fixed in
0.6.8
References Updated Sep 10, 2026 · Source: OSV.dev |
0.2.6
unknown
Dependencies (11)
+ 3 more |
|
0.2.5
unknown
1 CVE
GHSA-2rxc-gjrp-vjhx
RUSTSEC-2024-0404
Dec 04, 2024
Unsoundness in anstream
Medium
When given a valid UTF8 string "ö\x1b😀", the function in crates/anstream/src/adapter/strip.rs will be confused. The UTF8 bytes are \xc3\xb6 then \x1b then \xf0\x9f\x98\x80. When looping over "non-printable bytes" \x1b\xf0 will be considered as some non-printable sequence. This will produce a broken str from the incorrectly segmented bytes via str::from_utf8_unchecked, and that should never happen. Full credit goes to @Ralith who reviewed this code and asked @burakemir to follow up. Fixed in
0.6.8
References Updated Sep 10, 2026 · Source: OSV.dev |
0.2.5
unknown
Dependencies (11)
+ 3 more |
|
0.2.4
unknown
1 CVE
GHSA-2rxc-gjrp-vjhx
RUSTSEC-2024-0404
Dec 04, 2024
Unsoundness in anstream
Medium
When given a valid UTF8 string "ö\x1b😀", the function in crates/anstream/src/adapter/strip.rs will be confused. The UTF8 bytes are \xc3\xb6 then \x1b then \xf0\x9f\x98\x80. When looping over "non-printable bytes" \x1b\xf0 will be considered as some non-printable sequence. This will produce a broken str from the incorrectly segmented bytes via str::from_utf8_unchecked, and that should never happen. Full credit goes to @Ralith who reviewed this code and asked @burakemir to follow up. Fixed in
0.6.8
References Updated Sep 10, 2026 · Source: OSV.dev |
0.2.4
unknown
Dependencies (11)
+ 3 more |
|
0.2.3
unknown
1 CVE
GHSA-2rxc-gjrp-vjhx
RUSTSEC-2024-0404
Dec 04, 2024
Unsoundness in anstream
Medium
When given a valid UTF8 string "ö\x1b😀", the function in crates/anstream/src/adapter/strip.rs will be confused. The UTF8 bytes are \xc3\xb6 then \x1b then \xf0\x9f\x98\x80. When looping over "non-printable bytes" \x1b\xf0 will be considered as some non-printable sequence. This will produce a broken str from the incorrectly segmented bytes via str::from_utf8_unchecked, and that should never happen. Full credit goes to @Ralith who reviewed this code and asked @burakemir to follow up. Fixed in
0.6.8
References Updated Sep 10, 2026 · Source: OSV.dev |
0.2.3
unknown
Dependencies (11)
+ 3 more |