If you are regularly the fist target of zero-days your threat model should be stricter yes. The other 7.9 billion people in the world can afford to be a little less strict.
575 karma · joined June 25, 2014
If you are regularly the fist target of zero-days your threat model should be stricter yes. The other 7.9 billion people in the world can afford to be a little less strict.
So if you are trying to privilege escalate a linux box and sudo -l returns:
(root) /usr/sbin/tcpdump
You check gtfobins for tcpdump and see that you can get a root shell with sudo access.
Intel has clearly failed with regards to manufacturing new nodes, but is the chip design really that bad when they could compete for a long time with a large node disadvantage?
Shouldn't you replace AMD with TSMC in that sentence, unless you meant design instead of chips? AMD doesn't manufacture chips.
Here's one of the developers saying it is hard back in the WSL days.
https://github.com/Microsoft/WSL/issues/873#issuecomment-391...
The reason makes sense to me, but I'm not an expert. Maybe you could expand on why you think they could do it but chose not to?
https://docs.microsoft.com/en-us/windows/wsl/compare-version...
> As you can tell from the comparison table above, the WSL 2 architecture outperforms WSL 1 in several ways, with the exception of performance across OS file systems.
It's useful for me when developing dotnet intended for Linux as I can store the code in WSL and be able to build, debug, run docker and so on directly from vscode.
Isn't that exactly what watchtower does?
https://github.com/containrrr/watchtower
It works great on my mediacenter server running deluge, plex, sonarr, radarr, jackett and OpenVPN in docker.
Or are you talking about other ingredients?
>Important: If you enter your credit card info for age verification, Google will retain this data as necessary to meet legal and regulatory requirements.
Must be because of audit laws relating to processing credit cards.
https://support.google.com/accounts/answer/10071085?p=age-ve...
Like this for example:
However you could just catch Exception. Not sure why a parse error is a "Fatal error".
>Leaking KASLR/stack canary just mean you get 90s level triviality of attacking any stack-overflowing API you can find.
It does not seem trivial with this exploit, but maybe I'm just not getting it. With the low accuracy and transfer rate, it seems like a lot of stars need to line up with regards to how the service you attack function.
>More specifically, modern operating systems employ Kernel Address Space Layout Randomization (KASLR) and stack canaries. KASLR randomizes the location of the data structures and code used by the operating system, such that the location is unknown to an attacker. Stack canaries put secret values on the stack to detect whether an attacker has tampered with the stack. CacheOut extracts this information from the operating system, essentially enabling full exploitation via other software attacks, such such as buffer overflow attacks.
Can anyone explain this scenario? Is this really a realistic scenario? Do they mean if you have code execution on a system, and want to escalate privileges, you would find another network/socket service that is running on the same system, find an exploit in this service, and then leak the stack canary to allow corrupting the stack? There's often easier ways to defeat the stack canary.
This makes no sense. If you have the privileges to install a rootkit, there is no need to use any speculative execution exploit.
The site was created by Russians though, just not sure it is hosted there anymore.
That's not a speculative execution browser 0day, as it doesn't work in updated browsers and it never has (or I guess it works if you want to leak data you could just console.log). Could you post an actual 0day instead?
They leak in flight data, using a detached spidermonkey engine, patched to make performance.now() return rdtscp at a rate of 1B/s while the victim application is spamming a load string instruction as fast as possible.
This does not allow:
>any ad network can access any and all memory on your desktop
This allows any ad-network to access random bits on the cache line. If the timing mitigation didn't already fix this, it seems impossible to me to get anything useful from it, the precision and bitrate is just too low (which is why the exploit just spams load instructions in a while 1 loop).
>and the RIDL exploits don't require special instructions.
Weird, in the new addendum it says it uses TSX, and in the PoC it uses XBEGIN. Must be a mistake.
You can't use the speculative execution vulnerabilities to just read all system memory using a javascript exploit. Like the exploit that is the topic of this post can't be used in a browser at all, as you are limited to what the JIT executes, you can't just execute TSX instructions in a browser.
You might be thinking of when you have native code execution.