What versions of bitbucket contain the fixes for these CVEs?
Bitbucket Server running on Windows may be affected by CVE-2018-11233, if you have enabled any of the fsckObjects options ("fetch.fsckObjects", "receive.fsckObjects" or "transfer.fsckObjects") in any of your repositories, or globally for the Bitbucket Server user. For those running on Windows, we recommend updating Bitbucket Server with a patched version of Git. Information on updating Git can be found at https://confluence.atlassian.com/bitbucketserver/installing-and-upgrading-git-776640906.html.
Bitbucket Server itself is not vulnerable to CVE-2018-11235, regardless of platform, but we strongly recommend updating your client Git installations with a patched version of Git. The following versions of Git contain patches for CVE-2018-11233 and CVE-2018-11235:
Be aware that the advice found below for enabling transfer.fsckObjects can result in significantly higher disk and CPU usage when servicing clone, fetch, pull and push operations. We recommend monitoring system utilization to ensure the increased load doesn't cause performance issues. Additionally, once you have upgraded all of your Git clients we recommend disabling the transfer.fsckObjects option again.
transfer.fsckObjects
Additionally, after upgrading to a fixed version of Git on Bitbucket Server, you may want to consider globally enabling the transfer.fsckObjects Git option to help prevent exploitation of vulnerable Git client installations until all clients have been patched.
This can be done by running the following command as the user that Bitbucket Server runs as.
git config --global --bool <a href="https://extranet.atlassian.com/display/SECURITY/transfer.fsckObjects" target="_blank" rel="nofollow noopener noreferrer">transfer.fsckObjects</a>
true
Please refer to the article by the Atlassian Security team on this subject:
- Atlassian Products & Services and CVE-2018-11235 & CVE-2018-11233
This covers Bitbucket Server as well as the other Atlassian Products & services.
Thanks,
Caterina - Atlassian
Hi Roman,
You can find more information on the advisory page.
Bitbucket Server security advisories
I'll keep an eye on that page. It currently says "Last modified on Mar 1, 2018".
Sounds good. They will update the page accordingly if its an issue.
Is Bitbucket cloud affected by this vulnerability?
@Rabh Pandya,
No, Bitbucket Cloud is not affected by either vulnerability. However, for CVE-2018-11235, we still recommend updating client Git versions to ensure they're safe from any malicious repositories that may exist on any of the various hosting platforms.
Best regards,Bryan TurnerAtlassian Bitbucket
Just to offer a little clarification, Bitbucket Server itself is not vulnerable to either CVE, and does not need any patches of its own to address them. It's the Git binary installed on the server, which Bitbucket Server uses for various operations, that has the vulnerabilities and should be patched.
For CVE-2018-11235, Bitbucket Server does not use Git in a way that allows the submodules vulnerability to be exploited. (We cannot make any guarantees about what third-party apps installed in Bitbucket Server do, though; we can only say that nothing in the shipped product is exploitable.) As with CVE-2014-9390 from a few years back, the most important response to CVE-2018-11235 is upgrading Git on client systems.
For CVE-2018-11233, Bitbucket Server's default configuration does not use Git in a way that allows the NTFS vulnerability to be exploited. However, system administrators are able to make configuration changes that would render the system vulnerable. Because upgrading Git on Windows is typically quite simple, we recommend everyone running Bitbucket Server on Windows upgrade out of an abundance of caution.
This is just to clarify where the vulnerabilities lie. @Daniel's response remains the solution.
It looks like you're new here. Sign in or register to get started.
