Impacted Versions of OpenSSL:
The versions you want to see after you’ve updated OpenSSL are:
- new version will be .
- new version will be (that’s T-for-Tango at the end).
- new version will be (Zulu-Golf).
If you have these versions let’s see next what you should be doing and planning.
Companies need to patch their OpenSSL deployments. Pay particular attention to applications that bundle OpenSSL into their releases. Ensure you have an accurate inventory of all your hardware and software assets. Review your software database to determine your potential impact from these vulnerabilities. Be careful patching systems where applications have bundled in their own version of OpenSSL. If you have the means to scan systems with authentication, do so to ensure you have patched all installed versions of OpenSSL pre- and -post-patching. There are special circumstances to follow when patching Linux systems to be aware of. Review your OS vendors advisory for patching OpenSSL. Are their any workarounds to patching?
Emergency Workaround if Patching is not Possible:
There are currently no known work-arounds to alleviate these risks outside of patching. Now we move on to vulnerability management.
You have a Vulnerability Alert Management Process, right?
If you’re a subscriber to CyberHoot’s awareness training platform, you have access to our Policy and Process library which contains the Vulnerability Alert Management Process (VAMP) document. This document prescribes how to respond to situations like this and in what time frame. If your company has not yet adopted a VAMP-like process, now is a great time to get started.
If you’re a vCISO client, we’ve built this process for you and now you must execute according to the prescribed measures and timeframes. If you’re not a vCISO client or CyberHoot Product subscriber, perhaps you want to sign up here.