In January 2018 Google announced an attack that makes it practically possible to leak information from kernel memory on the host operating system.
We have discovered that CPU data cache timing can be abused to efficiently leak information out of mis-speculated execution, leading to (at worst) arbitrary virtual memory read vulnerabilities across local security boundaries in various contexts.
So far, there are three known variants of the issue:
- Variant 1: bounds check bypass (CVE-2017-5753).
- Variant 2: branch target injection (CVE-2017-5715).
- Variant 3: rogue data cache load (CVE-2017-5754).
Impact on Octopus Deploy
Octopus Deploy is not directly affected by these vulnerabilities. However, since the host operating system and underlying hardware can be vulnerable, any application running on affected systems can be affected. For your Octopus installation, this would include servers hosting:
- Octopus Server.
- Microsoft SQL Server which is hosting your Octopus database.
- The targets of your deployments.
The mitigation for these vulnerabilities are all related to the host operating system and underlying hardware. There is no specific mitigation for Octopus Deploy.
For Microsoft operating systems follow these security advisories to ensure your host operating system and underlying hardware are protected against these vulnerabilities:
- Guidance to mitigate speculative execution side-channel vulnerabilities
- Windows Client Guidance for IT Pros to protect against speculative execution side-channel vulnerabilities
For software and hardware from all other vendors, please follow the mitigation in each CVE report listed above.
Help us continuously improve
Please let us know if you have any feedback about this page.
Last updated Sunday, January 1, 2023