8 ms·
Great report on a critical RCE vulnerability in Slack. However, I will bite. $1,750 for a detailed report on a critical RCE is like rewarding sniffer-dogs with
by rvz 6y ago
Great report on a critical RCE vulnerability in Slack. However, I will bite.
$1,750 for a detailed report on a critical RCE is like rewarding sniffer-dogs with breadcrumbs. One could sell this exploit at least for 5 figures on the black market.
In all cases, since Electron brings XSS to the desktop, it is a hackers paradise.
- tptacek 6y agoCan you support that statement about the black market with evidence?
- arzel 6y agoagreed on 5 figures. evidence? there’s even clearnet websites where you can buy vulns. most known would be: https://0day.today https://0day.today
- viraptor 6y agoWhat you see on that website is the cost, not the earnings though. If a private exploit costs $1.2k, you can get 5 digits by selling it 9 times. That isn't a huge number of sales, but I don't know if this exploit would sell that many times. Anyway, by disclosing on H1 you're "selling" at most once.
- milofeynman 6y agohttps://en.m.wikipedia.org/wiki/Market_for_zero-day_exploits https://en.m.wikipedia.org/wiki/Market_for_zero-day_exploits https://en.m.wikipedia.org/wiki/Zerodium https://en.m.wikipedia.org/wiki/Zerodium
- tptacek 6y agoZerodium won't buy a Slack exploit. I'm not debating whether there is a black market for exploits; there is. It just doesn't buy most of the things HN commenters think it does.
- deleted 6y ago[deleted]
- deleted 6y ago[deleted]
- pansa2 6y ago> since Electron brings XSS to the desktop, it is a hackers paradise. Just curious - what makes XSS on the desktop different from other kinds of RCE vulnerability?
- slimsag 6y agoNothing, but if Slack was a web application and not an Electron application it would mean XSS would not immediately lead to RCE, you would need XSS and a vulnerability in the browser to get an RCE. Electron is basically that for you already: a vulnerable browser.
- wereHamster 6y agoI refuse to use the Slack desktop app, and use Slack only through a web browser. I trust Chrome (Google), Firefox (Mozilla), Safari (Apple) far more than the Slack engineers.
- deleted 6y ago[deleted]
- 0x0 6y agonodeIntegration:true
- greggman3 6y agoPart of this is Electron's environment and arguably fault. Electron used to default to insecure. You were basically running a web browser except with full access your entire machine file system/camera/mic/network etc. If you are an inexperienced developer it wasn't obvious that live linking to any 3rd party code could be an issue. Electron kind of fixed that. They warn you now and default to more secure. How many devs are capable of keeping it secure is up for debate. As a related issue, it used to be (maybe still is) that by default, links you click in Electron open in Electron. So you make any app that accepts user data and links and suddenly people are browsing the entire net in an un-secured browser. And worse, they break stuff. I made an electron app and explicitly made it so all links open in the user's browser. I updated to a new version and then to my horror found whatever I had done to make sure links opened in an external browser stopped opening links in an external browser. Native apps can have exploits but most native apps aren't designed to be an environment for running arbitrary code. They're only an app for working on data. Note, I love Electron, I've used it for several projects and it's great. But I'm also afraid of it and wish OSes were themselves more sandboxed so I didn't have to worry about it.
- laurent92 6y agoWhen running a security bounty, what makes me afraid is the compounding factor of finding the same kind of issue several times in different places, thereby multiplying the cost by 20. Of course $1750 is cheap, but I’d happily donate more if there is there were no risk of paying repeat bounties, given a week between them to fix each category of security failure I learn about. By the way, the security bounty should be mandatory to display to customers. It’s like saying “We don’t value the sum of all your data of all customers to more than $1750”.
- KMag 6y agoDon't bug bounties usually have some rules for splitting bounties or else paying only the first reporter in case of multiple independent discovery?
- thaumasiotes 6y agoIt is typical that only the first reporter gets a bounty; duplicate reports are usually given "duplicate" status. But you might have the same vulnerability found in several different places. Reports should really only be considered duplicates if the fix to one automatically fixes the other also. Your bug found in multiple locations might happen to be set up that way -- or it might not. This exact problem occurs frequently when a company with a bounty program makes an acquisition and brings the new software into scope for the program. The acquired code is often full of relatively easy-to-find, high-impact bugs. What I've seen people do in this case is open the scope, accept a certain number of reports, and then suspend eligibility for that software for a certain period of time. This would look like "we've had a lot of similar bugs filed against company-we-acquired.com, and we're taking that domain out of scope for X weeks while we work on it."
- thaumasiotes 6y ago(You could achieve exactly what laurent92 is asking for by taking an issue type ("SSRF") out of scope for a period.)
- onion2k 6y ago
- jansommer 6y agoDamn, didn't know $1750 was low. I got something similar for reporting an exploit to Microsoft, where opening an attached ICS/calendar entry in Outlooks web client allowed me to execute arbitrary JavaScript on outlook.microsoft.com as the current user. Should have asked for more!
- ianhawes 6y agoYes... yes you should have.
- dQw4w9WgXcQ 6y agoI wouldn't beat yourself up over it. There's probably room to develop an exploit valuation model that better helps to translate (time spent on research) + (X% of business/customer impact), where X is a pretty low figure, otherwise companies would never stay in business. Don't undervalue the intangible permanence of doing the right thing, character outlasts cash come the grave.
- tptacek 6y agoIt sounds like you got $1750 for an XSS-equivalent attack. That's high for XSS.
- justsomeuser 6y agoI found a XSS bug in a popular note taking app. It would allow an attacker to download all the users notes just by having them visit a URL. I reported it on HackerOne, it was only after I refused to post it on their free program that they added me to their paid private one. It was marked as "medium", I got $250 for it.
- tptacek 6y agoThat's a pretty normal price for an XSS.
- justsomeuser 6y agoDropbox and co pay $10,000 for the same exploit.
- tptacek 6y agoThen you should sell it to Dropbox, because $10,000 is extremely high for an XSS vulnerability.
- justsomeuser 6y agoI do not have the market rates for vulnerabilities, but I do know some pen testing companies charge $10,000 for a few days of work that may not return any concrete bugs. Compared with hiring a pen testing team, offering high bounties seems like a bargain as you get actual exploits that would impact the company.
- tptacek 6y agoYes, that is the premise behind bug bounties. If you're a vulnerability researcher with a track record, you will probably make better money and certainly more consistent money as a pentester. Many pentesters just do both. I have, uh, some experience with the rates here.