Zenoh-picoにメモリ破壊の脆弱性、1.10.2で修正
Summary
Eclipse Zenohの組み込み向け実装zenoh-picoに、受信メッセージの処理でメモリ破壊と機器停止を招く重大な脆弱性が公表されました。zenoh-picoを組み込んだ機器やファームウェアを持つ組織は、1.10.2で作り直して配布してください。
AI summary
Produced by SecPulse using an external AI model; it may contain mistakes. Check the original description and references below before acting on it.
Eclipse Zenohの組み込み向け実装zenoh-picoに、受信メッセージの処理でメモリ破壊と機器停止を招く重大な脆弱性が公表されました。zenoh-picoを組み込んだ機器やファームウェアを持つ組織は、1.10.2で作り直して配布してください。
Affected packages
| Package | Affected → Fixed | |
|---|---|---|
| Eclipse FoundationEclipse Zenoh (zenoh-pico) |
≥ 0.7.2-rc, < 1.10.2→ 1.10.2 |
1.10.2 |
Original description The description as published by the source.
Eclipse Zenoh's zenoh-pico implementation, versions 0.7.2-rc up to but excluding 1.10.2, does not validate the Zenoh identifier (ZID) length when deserializing timestamps. An attacker-controlled length greater than 16 causes an out-of-bounds write to a fixed 16-byte identifier buffer and causes the subsequent zero-fill operation to receive a negative length converted to a large unsigned size. Truncated timestamp inputs can also cause out-of-bounds reads or assertion failures. A remote attacker able to deliver crafted timestamp-bearing Zenoh messages through an accepted transport can cause memory corruption and denial of service, with potential remote code execution in builds lacking appropriate binary protections. This issue is fixed in version 1.10.2.
Depending on the release and message-decoding path, the unchecked timestamp identifier length causes a heap-based or stack-based buffer overflow. Ordinary-frame network message decoding moved from heap-backed storage to stack-local storage in version 1.5.0. Earlier affected releases already contained stack-based decoding paths, including reassembled fragmented messages.
Source: CVE.org (CVE Program・cvelistV5) NVD
References
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- patch github.com
- patch github.com
- web gitlab.eclipse.org
- web github.com
- web gitlab.eclipse.org