sirdarckcat

6 ms·

1.
by sirdarckcat 2y ago
It's just written by the CPU during a ucode update
2.
by sirdarckcat 2y ago
> This probably depends on a lot of non-public info: how does the PSP validate CPU state? https://github.com/amd/AMD-ASPFW/blob/3ca6650dd35d878b3fcbe5...
3.
by sirdarckcat 2y ago
> But raw write access to the flash depends on you being in SMM Look at tests/stop.sh and check the different segments (ls:, ms:, etc you can also address them like 0:[..], 1, 2, 3,... 15:[...]). One of those is probably flash. If y
4.
by sirdarckcat 2y ago
You can make a new instruction (or repurpose an existing one) that accesses physical memory bypassing the page walk, which would be faster. You can also make instructions that bypasses some checks (like privilege checks) and squeeze some ti
5.
by sirdarckcat 2y ago
We were not able to demonstrate that Zen5 is affected. If we end up doing so, we may release a new advisory or something.
6.
by sirdarckcat 2y ago
151515 is such an elitist number.. 3 * 13 * 37 * 3 * 5 * 7
7.
by sirdarckcat 3y ago
[citation needed] * ChromeOS, COS and Android are opensource, and they are all up to date. Mind elaborating?
8.
Hackceler8 – Google game hacking speedrun competition(twitter.com)
1 points by sirdarckcat 4y ago|0 comments
9.
by sirdarckcat 5y ago
> Sometimes I wish there was a Linux kernel security advisory process, but this would need funding or a dedicated volunteer. This is already happening https://osv.dev/list?q=Kernel&affected_only=true&page=1&ec
10.
by sirdarckcat 5y ago
for what is worth, the link gregkh pointed you to explains the answer for your first 2 points. Your last point is wrong. Simple example, which of the following thousand bugs are exploitable? https://syzkaller.appspot.com/ups
11.
Trick&Treat Paying Leets and Sweets for Linux Kernel Privescs and K8s Escapes(security.googleblog.com)
2 points by sirdarckcat 5y ago|0 comments
12.
by sirdarckcat 5y ago
about duplicates - google has this thing called grants https://bughunters.google.com/about/rules/5479188746993664 that pay people for doing security research, even if they don't find any bugs. we agree that d
13.
by sirdarckcat 5y ago
It can be tiring at times.
14.
by sirdarckcat 5y ago
Insecurity is invisible. Users have no way to know the weaknesses in the software they use until it's too late. Disclosure is meant to make it possible for users to see what weaknesses they might have so they can make informed decision
15.
by sirdarckcat 5y ago
Vulnerability deadlines are disclosure deadlines, not remediation deadlines. There's plenty of vulnerabilities that can't be fixed in that time, and I think it's fair for the public to know about them rather than keeping them
16.
by sirdarckcat 5y ago
Might be worth noting, 90 days are how long Google thinks it is reasonable to keep vulnerabilities secret without a fix. The longer it is kept secret, the benefits of the public knowing about it outweigh the risks. Not all vulnerabilities c
17.
by sirdarckcat 5y ago
Are you suggesting Google to make all unfixed vulnerabilities public after 90 days? Would that be even if the finder does not want them to become public? Or just as an opt-out type of thing.
18.
by sirdarckcat 5y ago
http://g.co/appsecurity has more details but TL;DR is that Google is supportive of people disclosing unfixed bugs after 90 days, which is what happened here.
19.
Tamper Dev Chrome Extension (edit HTTP requests/responses)(tamper.dev)
3 points by sirdarckcat 6y ago|0 comments
20.
HTTP Cache Cross-Site Leaks(sirdarckcat.blogspot.com)
2 points by sirdarckcat 8y ago|0 comments
21.
by sirdarckcat 9y ago
We added this section for the write-ups. We want to be able to republish write-ups and their code if we want.
22.
Announcing Google Capture the Flag 2017(security.googleblog.com)
42 points by sirdarckcat 9y ago|9 comments
23.
Unpatched (0day) JQuery Mobile XSS(sirdarckcat.blogspot.com)
2 points by sirdarckcat 10y ago|0 comments
24.
Creating a Decentralized Security Rewards Market(sirdarckcat.blogspot.com)
2 points by sirdarckcat 10y ago|0 comments
25.
Security Bugs Gallery(security.bugs.gallery)
4 points by sirdarckcat 11y ago|0 comments
26.
Google Security Reward Programs: Year in Review, Year in Preview(googleonlinesecurity.blogspot.com)
2 points by sirdarckcat 12y ago|0 comments
27.
by sirdarckcat 12y ago
The core library is in use in many Google products and runs across all browsers.
28.
JavaScript Apps Timing Attacks(sirdarckcat.blogspot.com)
1 points by sirdarckcat 12y ago|0 comments
29.
by sirdarckcat 12y ago
All security reports receive a "I filled a bug" after a bug is filled. https://www.google.com/search?q=%22Nice%20catch!%20I%27ve%20... Not a brush-off.
30.
by sirdarckcat 12y ago
Hi! Bounties are always awarded after the bug is disclosed[1]. We constantly[2] upgrade the bounties whenever we feel like we should be paying more, and we will continue to do so. We also increase the rewards from the amounts in the price l

More ›