Information Security News
In November, Heise, a german technology news publisher, broke a story that AVM cable modems included not only the manufacturers certificate authority certificate as part of the firmwarebut also the corresponding private key . The news didnt get a lot of attention back then. AVM is the maker of Fritz!Box routers and modems which are almost exclusively sold to german speaking countries only. When I read the news initially, I also considered it only a risk to cable modems in the area AVM operates. But it turns out, that the leak may have larger repercussions, as pointed out in a note published by CableLabs, the organization in charge of the DOCSIS cable modem standard. A reader forwarded us this note:
All operators globally may be exposed to a security issue related to the EuroDOCSIS PKI and need to take action. AVM cable modems were shipped with the device private key and the AVM CA private key in the firmware which is now publicly exposed. As a result illegitimate cable modems can be created which could cause network problems such as theft of service. Major CMTS vendors ship their product with both the DOCSIS and EuroDOCSIS Root CA installed as a trust anchor in their CMTSs. As a result, CableLabs recommends all operators blacklist (untrust) the compromised AVM CA in their CMTSs, regardless of whether or not they have AVM equipment deployed in their network or they actively use the EuroDOCSIS Root CA. 
So what does this all mean? DOCSIS is the standard cable modem operators adopted to allow manufacturers to create interoperable equipment. EuroDOCSIS is the European version of this standard. I will refer to both standards as DOCSIS going forward.
DOCSIS requires that each cable modem contains a unique certificate to authenticate the cable modem to the provider. The certificate is signed by the manufacturers CA, which in turn is signed using the DOCSIS CA. Cable modem operators trust cable modems that can present a properly signed certificate.
Due to AVMs mistake, the private key for AVMs is now public, and anybody could create new certificates that will be trusted by cable modem ISPs that trust the EuroDOCSIS CA. This could, for example, allow someone to spoof a cable modem owned by a different provider, or create a cable modem with rogue firmware that will not obey configurations sent by the ISP.
Heise in a follow-up story stated that the key was already used in the wild to sign fake certificates . The fake certificates were apparently used well before Heise broke the story.
As an end user, there is nothing you can do. As outlined by the note from CableLabs, ISPs will have to distrust the AVM CA. This could potentially cut service for users who use modems that provide certificates derived from the AVM CA. But most cable modem ISPs will not allow any modem to connect to their network, but only a subset of DOCSIS certified modems that are compatiblewith the particular head-end equipment used by the ISP. So the impact is likely small. AVM does not distribute cable-modems outside Europe as far as I know, but I may be wrong.
https://www.heise.de/security/meldung/AVM-entweicht-geheimer-FritzBox-Schluessel-3463752.html (German Only)
OpenSSL released an update for OpenSSL 1.1.0. The latest version is now OpenSSL 1.1.0e. OpenSSL 1.0.2 is not affected.
The vulnerability, %%cve:2017-3733%% can lead to a crash in either clients or servers. In order to trigger the vulnerability, an attacker would first negotiate an SSL connection without the Encrypt-Then-Mac extension. Later, the attacker would use the extension during a renegotiation handshake. The vulnerability is rated as High by OpenSSL, below the maximum level of Critical.
I recommend you wait for your respective vendor/Linux distribution to provide an updated OpenSSL library, which should be available shortly if it isnt already available. Not too many systems are using OpenSSL 1.1.0. Many current Linux distribution use the non-vulnerable1.0.2 branch. So no need to panic.
Microsoft earlier today updated its blog post about the skipped February patch Tuesday with a note that We will deliver updates as part of the planned March Update Tuesday, March 14, 2017. March 14th is the March Patch Tuesday date, so Februarys updates will be combined with the March update. Probably overall the least disruptive solution at this point.