string-interner
Activity
- Latest release
- 4mo ago
- Total releases
- 35
- Cadence
- ~10 days
- Last 12 months
- 1
Details
- License
- MIT/Apache-2.0
- First release
- Feb 06, 2017
| Version | Released | |
|---|---|---|
0.20.0
unknown
|
0.20.0
unknown
Dependencies (5)
|
|
0.19.0
unknown
|
0.19.0
unknown
Dependencies (5)
|
|
0.18.0
unknown
|
0.18.0
unknown
Dependencies (5)
|
|
0.17.0
unknown
|
0.17.0
unknown
Dependencies (6)
|
|
0.16.0
unknown
|
0.16.0
unknown
Dependencies (6)
|
|
0.15.0
unknown
|
0.15.0
unknown
Dependencies (6)
|
|
0.14.0
unknown
|
0.14.0
unknown
Dependencies (6)
|
|
0.13.0
unknown
|
0.13.0
unknown
Dependencies (6)
|
|
0.12.2
unknown
|
0.12.2
unknown
Dependencies (8)
|
|
0.12.1
unknown
|
0.12.1
unknown
Dependencies (8)
|
|
0.12.0
unknown
|
0.12.0
unknown
Dependencies (8)
|
|
0.11.3
unknown
|
0.11.3
unknown
Dependencies (8)
|
|
0.11.2
unknown
|
0.11.2
unknown
Dependencies (8)
|
|
0.11.1
unknown
|
0.11.1
unknown
Dependencies (8)
|
|
0.11.0
unknown
yanked
|
0.11.0
unknown
yanked
Dependencies (8)
|
|
0.10.1
unknown
|
0.10.1
unknown
Dependencies (5)
|
|
0.10.0
unknown
|
0.10.0
unknown
Dependencies (5)
|
|
0.9.0
unknown
|
0.9.0
unknown
Dependencies (5)
|
|
0.8.0
unknown
|
0.8.0
unknown
Dependencies (5)
|
|
0.6.4
unknown
|
0.6.4
unknown
Dependencies (3)
|
|
0.7.1
unknown
|
0.7.1
unknown
Dependencies (4)
|
|
0.7.0
unknown
yanked
1 CVE
CVE-2019-16882
GHSA-49fq-pw77-6qxj
RUSTSEC-2019-0023
Aug 25, 2021
Use after free in string-interner
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
Affected versions of this crate did not clone contained strings when an interner is cloned. Interners have raw pointers to the contained strings, and they keep pointing the strings which the old interner owns, after the interner is cloned. If a new cloned interner is alive and the old original interner is dead, the new interner has dangling pointers to the old interner's storage, which is already dropped. This allows an attacker to read the already freed memory. The dangling pointers are used by the interners to check a string is already interned. An attacker can do brute force attack to get the data pointed by the dangling pointer. Fixed in
0.6.4
0.7.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.7.0
unknown
yanked
Dependencies (4)
|
|
0.6.3
unknown
yanked
1 CVE
CVE-2019-16882
GHSA-49fq-pw77-6qxj
RUSTSEC-2019-0023
Aug 25, 2021
Use after free in string-interner
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
Affected versions of this crate did not clone contained strings when an interner is cloned. Interners have raw pointers to the contained strings, and they keep pointing the strings which the old interner owns, after the interner is cloned. If a new cloned interner is alive and the old original interner is dead, the new interner has dangling pointers to the old interner's storage, which is already dropped. This allows an attacker to read the already freed memory. The dangling pointers are used by the interners to check a string is already interned. An attacker can do brute force attack to get the data pointed by the dangling pointer. Fixed in
0.6.4
0.7.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.6.3
unknown
yanked
Dependencies (3)
|
|
0.6.2
unknown
yanked
1 CVE
CVE-2019-16882
GHSA-49fq-pw77-6qxj
RUSTSEC-2019-0023
Aug 25, 2021
Use after free in string-interner
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
Affected versions of this crate did not clone contained strings when an interner is cloned. Interners have raw pointers to the contained strings, and they keep pointing the strings which the old interner owns, after the interner is cloned. If a new cloned interner is alive and the old original interner is dead, the new interner has dangling pointers to the old interner's storage, which is already dropped. This allows an attacker to read the already freed memory. The dangling pointers are used by the interners to check a string is already interned. An attacker can do brute force attack to get the data pointed by the dangling pointer. Fixed in
0.6.4
0.7.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.6.2
unknown
yanked
Dependencies (3)
|
|
0.6.1
unknown
yanked
1 CVE
CVE-2019-16882
GHSA-49fq-pw77-6qxj
RUSTSEC-2019-0023
Aug 25, 2021
Use after free in string-interner
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
Affected versions of this crate did not clone contained strings when an interner is cloned. Interners have raw pointers to the contained strings, and they keep pointing the strings which the old interner owns, after the interner is cloned. If a new cloned interner is alive and the old original interner is dead, the new interner has dangling pointers to the old interner's storage, which is already dropped. This allows an attacker to read the already freed memory. The dangling pointers are used by the interners to check a string is already interned. An attacker can do brute force attack to get the data pointed by the dangling pointer. Fixed in
0.6.4
0.7.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.6.1
unknown
yanked
Dependencies (3)
|
|
0.6.0
unknown
yanked
1 CVE
CVE-2019-16882
GHSA-49fq-pw77-6qxj
RUSTSEC-2019-0023
Aug 25, 2021
Use after free in string-interner
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
Affected versions of this crate did not clone contained strings when an interner is cloned. Interners have raw pointers to the contained strings, and they keep pointing the strings which the old interner owns, after the interner is cloned. If a new cloned interner is alive and the old original interner is dead, the new interner has dangling pointers to the old interner's storage, which is already dropped. This allows an attacker to read the already freed memory. The dangling pointers are used by the interners to check a string is already interned. An attacker can do brute force attack to get the data pointed by the dangling pointer. Fixed in
0.6.4
0.7.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.6.0
unknown
yanked
Dependencies (3)
|
|
0.5.0
unknown
yanked
1 CVE
CVE-2019-16882
GHSA-49fq-pw77-6qxj
RUSTSEC-2019-0023
Aug 25, 2021
Use after free in string-interner
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
Affected versions of this crate did not clone contained strings when an interner is cloned. Interners have raw pointers to the contained strings, and they keep pointing the strings which the old interner owns, after the interner is cloned. If a new cloned interner is alive and the old original interner is dead, the new interner has dangling pointers to the old interner's storage, which is already dropped. This allows an attacker to read the already freed memory. The dangling pointers are used by the interners to check a string is already interned. An attacker can do brute force attack to get the data pointed by the dangling pointer. Fixed in
0.6.4
0.7.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.5.0
unknown
yanked
|
|
0.4.0
unknown
yanked
1 CVE
CVE-2019-16882
GHSA-49fq-pw77-6qxj
RUSTSEC-2019-0023
Aug 25, 2021
Use after free in string-interner
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
Affected versions of this crate did not clone contained strings when an interner is cloned. Interners have raw pointers to the contained strings, and they keep pointing the strings which the old interner owns, after the interner is cloned. If a new cloned interner is alive and the old original interner is dead, the new interner has dangling pointers to the old interner's storage, which is already dropped. This allows an attacker to read the already freed memory. The dangling pointers are used by the interners to check a string is already interned. An attacker can do brute force attack to get the data pointed by the dangling pointer. Fixed in
0.6.4
0.7.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.4.0
unknown
yanked
|
|
0.3.3
unknown
1 CVE
CVE-2019-16882
GHSA-49fq-pw77-6qxj
RUSTSEC-2019-0023
Aug 25, 2021
Use after free in string-interner
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
Affected versions of this crate did not clone contained strings when an interner is cloned. Interners have raw pointers to the contained strings, and they keep pointing the strings which the old interner owns, after the interner is cloned. If a new cloned interner is alive and the old original interner is dead, the new interner has dangling pointers to the old interner's storage, which is already dropped. This allows an attacker to read the already freed memory. The dangling pointers are used by the interners to check a string is already interned. An attacker can do brute force attack to get the data pointed by the dangling pointer. Fixed in
0.6.4
0.7.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.3.3
unknown
|
|
0.3.2
unknown
1 CVE
CVE-2019-16882
GHSA-49fq-pw77-6qxj
RUSTSEC-2019-0023
Aug 25, 2021
Use after free in string-interner
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
Affected versions of this crate did not clone contained strings when an interner is cloned. Interners have raw pointers to the contained strings, and they keep pointing the strings which the old interner owns, after the interner is cloned. If a new cloned interner is alive and the old original interner is dead, the new interner has dangling pointers to the old interner's storage, which is already dropped. This allows an attacker to read the already freed memory. The dangling pointers are used by the interners to check a string is already interned. An attacker can do brute force attack to get the data pointed by the dangling pointer. Fixed in
0.6.4
0.7.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.3.2
unknown
|
|
0.3.1
unknown
1 CVE
CVE-2019-16882
GHSA-49fq-pw77-6qxj
RUSTSEC-2019-0023
Aug 25, 2021
Use after free in string-interner
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
Affected versions of this crate did not clone contained strings when an interner is cloned. Interners have raw pointers to the contained strings, and they keep pointing the strings which the old interner owns, after the interner is cloned. If a new cloned interner is alive and the old original interner is dead, the new interner has dangling pointers to the old interner's storage, which is already dropped. This allows an attacker to read the already freed memory. The dangling pointers are used by the interners to check a string is already interned. An attacker can do brute force attack to get the data pointed by the dangling pointer. Fixed in
0.6.4
0.7.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.3.1
unknown
|
|
0.3.0
unknown
1 CVE
CVE-2019-16882
GHSA-49fq-pw77-6qxj
RUSTSEC-2019-0023
Aug 25, 2021
Use after free in string-interner
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
Affected versions of this crate did not clone contained strings when an interner is cloned. Interners have raw pointers to the contained strings, and they keep pointing the strings which the old interner owns, after the interner is cloned. If a new cloned interner is alive and the old original interner is dead, the new interner has dangling pointers to the old interner's storage, which is already dropped. This allows an attacker to read the already freed memory. The dangling pointers are used by the interners to check a string is already interned. An attacker can do brute force attack to get the data pointed by the dangling pointer. Fixed in
0.6.4
0.7.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.3.0
unknown
|
|
0.2.1
unknown
1 CVE
CVE-2019-16882
GHSA-49fq-pw77-6qxj
RUSTSEC-2019-0023
Aug 25, 2021
Use after free in string-interner
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
Affected versions of this crate did not clone contained strings when an interner is cloned. Interners have raw pointers to the contained strings, and they keep pointing the strings which the old interner owns, after the interner is cloned. If a new cloned interner is alive and the old original interner is dead, the new interner has dangling pointers to the old interner's storage, which is already dropped. This allows an attacker to read the already freed memory. The dangling pointers are used by the interners to check a string is already interned. An attacker can do brute force attack to get the data pointed by the dangling pointer. Fixed in
0.6.4
0.7.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.2.1
unknown
|
|
0.2.0
unknown
1 CVE
CVE-2019-16882
GHSA-49fq-pw77-6qxj
RUSTSEC-2019-0023
Aug 25, 2021
Use after free in string-interner
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
Affected versions of this crate did not clone contained strings when an interner is cloned. Interners have raw pointers to the contained strings, and they keep pointing the strings which the old interner owns, after the interner is cloned. If a new cloned interner is alive and the old original interner is dead, the new interner has dangling pointers to the old interner's storage, which is already dropped. This allows an attacker to read the already freed memory. The dangling pointers are used by the interners to check a string is already interned. An attacker can do brute force attack to get the data pointed by the dangling pointer. Fixed in
0.6.4
0.7.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.2.0
unknown
Dependencies (1)
|
|
0.1.0
unknown
1 CVE
CVE-2019-16882
GHSA-49fq-pw77-6qxj
RUSTSEC-2019-0023
Aug 25, 2021
Use after free in string-interner
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
Affected versions of this crate did not clone contained strings when an interner is cloned. Interners have raw pointers to the contained strings, and they keep pointing the strings which the old interner owns, after the interner is cloned. If a new cloned interner is alive and the old original interner is dead, the new interner has dangling pointers to the old interner's storage, which is already dropped. This allows an attacker to read the already freed memory. The dangling pointers are used by the interners to check a string is already interned. An attacker can do brute force attack to get the data pointed by the dangling pointer. Fixed in
0.6.4
0.7.1
References
Updated Nov 08, 2023 · Source: OSV.dev |
0.1.0
unknown
|