https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 19 Oct 2026 15:06:54 +0000 https://cve.radiocsirt.org/vuln/cve-2020-36435 <p>An issue was discovered in the ruspiro-singleton crate before 0.4.1 for Rust. In Singleton, Send and Sync do not have bounds checks.</p> <p>An issue was discovered in the ruspiro-singleton crate before 0.4.1 for Rust. In Singleton, Send and Sync do not have bounds checks.</p> https://cve.radiocsirt.org/vuln/cve-2020-36435 https://cve.radiocsirt.org/vuln/ghsa-fqq2-xp7m-xvm8 <p><strong>Affected:</strong> crates.io: ruspiro-singleton</p> <p>`Singleton&lt;T&gt;` is meant to be a static object that can be initialized lazily. In order to satisfy the requirement that `static` items must implement `Sync`, `Singleton` implemented both `Sync` and `Send` unconditionally.</p> <p>This allows for a bug where non-`Sync` types such as `Cell` can be used in singletons and cause data races in concurrent programs.</p> <p>The flaw was corrected in commit `b0d2bd20e` by adding trait bounds, requiring the contaiend type to implement `Sync`.</p> <p><strong>Affected:</strong> crates.io: ruspiro-singleton</p> <p>`Singleton&lt;T&gt;` is meant to be a static object that can be initialized lazily. In order to satisfy the requirement that `static` items must implement `Sync`, `Singleton` implemented both `Sync` and `Send` unconditionally.</p> <p>This allows for a bug where non-`Sync` types such as `Cell` can be used in singletons and cause data races in concurrent programs.</p> <p>The flaw was corrected in commit `b0d2bd20e` by adding trait bounds, requiring the contaiend type to implement `Sync`.</p> https://cve.radiocsirt.org/vuln/ghsa-fqq2-xp7m-xvm8