security-research-pocs
retbleed
security-research-pocs | retbleed | |
---|---|---|
5 | 1 | |
1,814 | 144 | |
- | 2.8% | |
1.5 | 2.7 | |
about 3 years ago | 4 months ago | |
C++ | C | |
Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
security-research-pocs
-
A call to reconsider Linux address-space isolation
> Suppose I'm a typical desktop user, how is important information going to be stolen if I have mitigations turned off and JavaScript enabled?
https://github.com/google/security-research-pocs/tree/master...
I don't imagine I'm going to explain it better than the many others who have already done so.
> What state does my browser have to be in, and what actions do I have to take (or not take) for the attack to succeed?
Your browser would have to be pretty old/ outdated since they've been updated to mitigate these attacks.
> What likelihood is it that someone has deployed an attack that meets those requirements?
That's not a simple question. Threat landscapes change based on a lot of factors. As I said earlier, we won't see these attacks because people have already patched and attackers have other methods.
> So we agree it's OK to leave mitigations off and browse the web?
You can do whatever you want, idk what you're trying to ask here. What is "OK" ? You will be vulnerable but unlikely to be attacked for the reasons mentioned. If you are "OK" with that that's up to you.
-
Intel and AMD CPUs vulnerable to a new speculative execution attack (RETBLEED)
Those attacks relied on performance.now() https://github.com/google/security-research-pocs/blob/d10780...
Chrome has limited "performance.now" to have a relatively low resolution: https://chromium-review.googlesource.com/c/chromium/src/+/85...
Also, "2018 install of win10", you might have already been patched during install.
Microsoft rolled out specture/meltdown mitigations at the OS level in January 2018.
-
New Spectre Vulnerability Version Beats All Mitigations, Performance to Badly Degrade After the Fix
That said, I'm using 'arbitrary' to mean any algorithm can be downloaded and ran without the user doing much; JS is Turing Complete. Additionally, older browsers' JS engines (at least the configuration of them) were feature-rich enough to do the relevant exploits.
- Spectre JavaScript PoCs
- Google released proof-of-concept code to conduct Spectre attacks against its Chrome browser to share knowledge of browser-based side-channel attacks.
retbleed
-
Intel and AMD CPUs vulnerable to a new speculative execution attack (RETBLEED)
I'm probably doing it wrong, but I'm getting SIGILL on Haswell for ret_bti and break_kaslr from the demo: https://github.com/comsec-group/retbleed
Though it seems like the code is not portable (?) between CPU microarchitectures.
What are some alternatives?
scrypt - The scrypt key derivation function was originally developed for use in the Tarsnap online backup system and is designed to be far more secure against hardware brute-force attacks than alternative functions such as PBKDF2 or bcrypt.