7 ms·
You can't contain me: elevation-of-privilege vulnerability in Docker for Windows
- shshhdhs 8y ago> Docker at first denied a vulnerability existed at all, but later patched it on July 19th. After further discussions, they assigned CVE-2018-15514 on the 18th August. It’s frustrating that this is the default reaction. I know why it occurs, at least from a human psychological standpoint, but it’s still frustrating. I’ve reported vulnerabilities without response, only to find them thanklessly fixed later. Without reply. But most of the time, my notifications are ignored. It becomes depressing very quickly.
- jlawson 8y agoAre there possible legal consequences to acknowledging such a report, though? Maybe it's not just psychological, but a CYA move.
- scaryclam 8y agoIt's unlikely. Many companies handle this sort of thing every day and don't deny the issue, just delay confirmation. It's more likely that someone within Docker decided that they didn't believe the report, but didn't bother to investigate properly before responding.
- Kalium 8y agoGenerally no, there is minimal liability attached to acknowledging a report. There may be internal political issues and definitely external media ones, though. Nobody wants to be the person who says "We're vulnerable, but I don't care enough to fix it". That's how you get internal political battles. Denial solves that problem. When dealing with external reports, it means ammunition for dealing with third parties. "We are not aware of any such vulnerabilities" becomes a defensible position, as does telling reporters that you dispute the claims of vulnerability. Those buy time to maybe fix something. And, well, there's the CYA psychology too. Nobody wants to confront the idea that they, or their smart and hard-working coworkers, screwed up to the point of creating a significant vulnerability.
- kerng 8y agoSomething similar happened to me with Amazon a while back. Found some vulns, and they fixed them but never publicly acknowledged them - because they said "the cloud is always patched", so no need to tell anyone- which I thought was an odd response.
- rocketChat 8y agoSame for the RocketChat developers: https://github.com/RocketChat/Rocket.Chat/pull/10793 https://github.com/RocketChat/Rocket.Chat/pull/10793 "We do not disclose security fixes as soon we have them fixed to prevent bad guys to exploit them." "as soon we have" means never. They believe bad guys would not monitor the commits of target products.
- lysp 8y agoNot disclosing in release change logs potentially increase the chance of people being affected. If I see a changelog with XSS fixed I will update a product straight away, if I don't - I might leave it a week or two until I have time.
- ctz 8y agoI had a similar experience a few years back with Google (specifically the Android security team). Eager to get the issue fixed, but not in public disclosure or acknowledgement.
- bdcravens 8y agoPersonally I've been turned off by Docker the company on numerous occasions. (Still love docker the project) Are there any inroads to a truly open source implementation of Docker for Mac and Windows? (Though I assume running a Linux VM would suffice?) It seems unfortunate that the default is running a non-open binary.
- hrcxxx 8y agoIf you are developing with docker, you should use mac or linux anyway. Windows is for Office tools and watching movies.
- raesene9 8y agoLinux I could understand but not MacOS. Of the three major desktop platforms, it's the only one without native containerization support...
- pjmlp 8y agoSo what is missing ? https://developer.apple.com/documentation/hypervisor https://developer.apple.com/documentation/hypervisor https://developer.apple.com/app-sandboxing/ https://developer.apple.com/app-sandboxing/ https://developer.apple.com/documentation/security/authorization_services https://developer.apple.com/documentation/security/authoriza...
- cntainer 8y agoNot really missing anything, it's just that on macOS you actually need a vm to run docker. Docker for mac uses HyperKit VM and starts docker containers inside it. It's mostly the same on windows (you needed hyper-v or virtualbox to run docker) but they are making efforts to run containers natively. Not sure how far they got with that. In the end if you want the best performance with minimum resource usage you need a Linux OS
- Jare 8y agoTo clarify, my understanding is that on Windows you will always need a VM to run Linux containers, but there will be (is?) native Windows containers. The dream is that maybe one day WSL will fully support Linux containers without a vm, but I will be amazed if they can pull that off.
- barrkel 8y ago
- nneonneo 8y agoOn Linux, at least, being able to access the docker daemon (i.e. being in the docket group) is essentially equivalent to being root, in that there are trivial ways to become root if you can start an arbitrary container (e.g. bind-mounting / into a container). So, it’s perhaps unclear how this exploit is significantly worse. Yes, you get access to SYSTEM, but Docker’s permission model appears to be predominantly “if you can control Docker then you own the machine”. Is this not the case on Windows?
- deleted 8y ago[deleted]
- deleted 8y ago[deleted]
- zapita 8y agoThe difference as I understand it is documentation. For Linux, the Docker docs make it abundantly clear what the security model is - don’t give access to the daemon socket to anyone you don’t trust to be root. For Windows on the other hand there seems to be no official documentation on the topic. Instead some “unofficial” documentation has popped up to fill the void, making insecure recommendations in the process. This then becomes Docker’s problem. I think it’s a good general lesson for documenting a platform: in the end you are responsible not only for what you explain to your users, but also for what they explain to each other. This can be frustrating because it makes you responsible for something you cannot control, like Docker couldn’t control the recommendations on that github thread. But you are still on the hook for addressing it - in this case probably by filling the gap in official documentation.
- tjoff 8y ago> This can be frustrating because it makes you responsible for something you cannot control If bad recommendations are a product of bad/non-existent documentation then that very much is something you can control and a direct consequence of that neglect. If docker couldn't be bothered the blame should not be with the bad recommendations.
- deleted 8y ago
- anyzen 8y agoWhat is that about? - 2018-04-03 - Verified existing and sent to iDefense’s VCP - 2018-04-04 - Validated and acquired by iDefense Is there a company that buys information about bugs ahead of time so they can protect their clients? (a cursory Internet search didn't answer my question)
- rhplus 8y agoIs there a company that buys information about bugs ahead of time so they can protect their clients? Companies like Zerodium act as brokers for 0-day exploits, but they tend to sell only to government agencies and the like. https://zerodium.com/about.html https://zerodium.com/about.html
- anyzen 8y agoAnd iDefense is doing something similar?
- dewey 8y agoThey are more "security alerts as a service": https://searchsecurity.techtarget.com/feature/VeriSign-iDefense-Threat-intelligence-services-overview https://searchsecurity.techtarget.com/feature/VeriSign-iDefe...
- wyldfire 8y agoGee. Is that really ethical? Presumably their customers don't intend to patch the bugs without help from the vendor. They likely intend to exploit the bugs (in the name of state surveillance). Many/most global governments (all?) aren't trustworthy in this regard. If you disclose a bug to Zerodium, can you trust them not to have "bad" governments as customers? Also, consider a Sybil attack: Zerodium is an untrustworthy government front. > ZERODIUM customers are mainly government organizations in need of specific and tailored cybersecurity capabilities, as well as major corporations from defense, technology, and financial sectors, in need of protective solutions to defend against zero-day attacks. shrug, okay, I hope that's the case.