But if you’re hoping I can shed some light on what the vulnerability is, I’m sorry. I can’t help.
In a mailing list posting, developer Mark J Cox announced the new version of the code in the briefest fashion possible:
The OpenSSL project team would like to announce the forthcoming release of OpenSSL versions 1.0.2d and 1.0.1p.
These releases will be made available on 9th July. They will fix a single security defect classified as “high” severity. This defect does not affect the 1.0.0 or 0.9.8 releases.
Fingers crossed, this new vulnerability in OpenSSL won’t be anything like as serious as Heartbleed – but the grading of it as “high severity” means that it could open the door to various threats: ranging from fairly tame denial-of-service attacks to rather unpleasant remote code execution.
Don’t be too upset that the OpenSSL project is keeping details of the vulnerability under its hat for now. No doubt they will be concerned that any information they share in advance could be exploited in live hacks by malicious hackers.
Being careful about vulnerability disclosure is particularly important when the software is so widely used, and understood to be an essential component required in securing internet transactions.
Nobody enjoys thinking about the risks associated with having a security bug in essential code used by so many internet services – especially before a special patch is ready for mainstream use.
But at least you can be reassured that patches are on their way, and that the OpenSSL team is not resting on its laurels.
So, listen up system administrators and developers. When the update fixing the OpenSSL vulnerability does arrive sometime on Thursday, be sure to patch as soon as possible. You owe it to your own security, but also in order to properly protect the security of your partners and customers.
Found this article interesting? Follow Graham Cluley on Twitter to read more of the exclusive content we post.