Lucene search
K

8 matches found

Github Security Blog
Github Security Blog
added 2023/10/24 7:22 p.m.25 views

Sequential calls of encryption API (`encrypt`, `wrap`, and `dump`) result in nonce reuse

Problem: Trying to create a new encrypted message with the same cocoon object generates the same ciphertext. It mostly affects MiniCocoon and Cocoon objects with custom seeds and RNGs where StdRng is used under the hood. Note: The issue does NOT affect objects created with Cocoon::new which...

4.5CVSS6.8AI score0.0003EPSS
Exploits0References6Affected Software1
OSV
OSV
added 2021/08/25 8:50 p.m.12 views

GHSA-M9M5-CG5H-R582 Improper random number generation in nanorand

In versions of nanorand prior to 0.5.1, RandomGen implementations for standard unsigned integers could fail to properly generate numbers, due to using bit-shifting to truncate a 64-bit number, rather than just an as conversion. This often manifested as RNGs returning nothing but 0, including the...

5.1CVSS9.4AI score0.00433EPSS
Exploits0References5
RustSec
RustSec
added 2021/02/12 12:0 p.m.20 views

Incorrect check on buffer length when seeding RNGs

Summary: randcore::le::readu32into and readu64into have incorrect checks on the source buffer length, allowing the destination buffer to be under-filled. Implications: some downstream RNGs, including Hc128Rng but not the more widely used ChaChaRng, allow seeding using the SeedableRng::fromseed...

9.8CVSS2.2AI score0.00468EPSS
Exploits0Affected Software1
RustSec
RustSec
added 2020/12/09 12:0 p.m.16 views

nanorand 0.5.0 - RNGs failed to generate properly for non-64-bit numbers

In versions of nanorand prior to 0.5.1, RandomGen implementations for standard unsigned integers could fail to properly generate numbers, due to using bit-shifting to truncate a 64-bit number, rather than just an as conversion. This often manifested as RNGs returning nothing but 0, including the...

9.8CVSS2.8AI score0.00433EPSS
Exploits0Affected Software1
OSV
OSV
added 2020/12/09 12:0 p.m.14 views

RUSTSEC-2020-0089 nanorand 0.5.0 - RNGs failed to generate properly for non-64-bit numbers

In versions of nanorand prior to 0.5.1, RandomGen implementations for standard unsigned integers could fail to properly generate numbers, due to using bit-shifting to truncate a 64-bit number, rather than just an as conversion. This often manifested as RNGs returning nothing but 0, including the...

5.1CVSS9.4AI score0.00433EPSS
Exploits0References3
Filippo.io
Filippo.io
added 2020/02/09 11:0 p.m.19 views

The Linux CSPRNG Is Now Good!

Oceans of ink and hours on stage have been spent to convince the world that the best random number generator is /dev/urandom, the kernel one. And it is, and its always been. However, an uncomfortable truth was that the Linux CSPRNG really could have been better than it was. Userspace CSPRNGs...

7.1AI score
Exploits0
ThreatPost
ThreatPost
added 2014/03/14 11:55 a.m.7 views

Dennis Fisher and Mike Mimoso Discuss CanSecWest and Pwn2Own

Dennis Fisher and Mike Mimoso talk about the news from the CanSecWest conference, the drama and melodrama at Pwn2Own and the bad year that RNGs have had. Download: digitalunderground148.mp3 Photo via mayanais‘ Flickr photostream, Creative Commons...

3.3AI score
Exploits0References3
ThreatPost
ThreatPost
added 2013/10/18 12:19 p.m.11 views

/Dev/Random PRNG in Linux Questioned

The sanctity of the dev/random random number generator used in the Linux kernel has been a hot-button issue for more than a month. A petition posted to change.org in September to remove RdRand from dev/random, for example, was met with fury from Linus Torvalds who called the developer who posted ...

0.1AI score
Exploits0References4
Rows per page
Query Builder