Potential Undefined Behavior via Unsafe String Conversion in Eclipse iceoryx2’s StaticString
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Eclipse Foundation | Eclipse iceoryx™ | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Eclipse | Iceoryx |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.153% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Eclipse
Eclipse iceoryx |
|
| Vendors & Products |
Eclipse
Eclipse iceoryx |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Potential Undefined Behavior via Unsafe String Conversion in Eclipse iceoryx2’s StaticString |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In Eclipse iceoryx2 versions greater than v0.8.0, the StaticString exposes its contents as mutable bytes through safe APIs, while String::as_str() converts those bytes into a Rust string slice without validating UTF-8. An application can therefore create an invalid &str and trigger undefined behavior using entirely safe Rust. | |
| Weaknesses | CWE-749 | |
| References |
| |
| Metrics |
cvssV4_0
|