Patched: Regarding Spectre & Meltdown

Code42 is aware of the identified vulnerability in regards to servers running on Intel's technology. Currently, Code42 is assessing the risk and impact to our company and our customers. Security is our top priority, and we will be taking all necessary actions to further protect against this vulnerability.

Have more questions? Submit a request

2 Comments

  • 0
    Avatar
    Molly R

    Code42 is aware of the identified processor vulnerabilities commonly referred to as Spectre and Meltdown. We anticipate deploying patches to address this issue over the next few weeks. The deployments will depend on patch availability from our vendors and will be deployed in a orderly fashion after thorough testing to ensure that customer impacts are minimized.

    If you have data stored in our cloud, we are planning on deploying the patches during our normally scheduled System Maintenance periods as the patches become available and after they have passed internal testing. For more information on our maintenance times, please go to https://support.code42.com/Terms_and_conditions/Code42_customer_support_resources/Scheduled_maintenance

    If you have a Code42 managed appliance, our Enterprise Cloud Management team will reach out to you to schedule a time for installation of patches to CloudOS after they have passed internal testing. This will require a restart of your server.

    In the meantime, the following links may be helpful in further understanding the vulnerability:

    Spectre/Meltdown summary page: https://spectreattack.com/#faq-fix

    MITRE pages on the vulnerabilities:

  • 0
    Avatar
    Molly R

    We have had customers follow up with us on the status of this maintenance.

    Patches to the Code42 Cloud were deployed across multiple weeks of maintenance windows, and this change has been complete in our cloud since March 6, 2018.

    If you have a Code42 managed appliance, our Enterprise Cloud Management team is available to schedule a time for installation of patches to CloudOS if you have not already done so. This will require a restart of your server.

Article is closed for comments.
Powered by Zendesk