Not because it's not important, but because it just desensitizes the whole impact of vulnerabilities the caliber of Heartbleed or Shellshock which did affect a large chunk of the servers and machines connected to the internet at the time.
Now they claim it's bigger than heartbleed, but with no exploit, and no clear statement on what actual in use implementations are affected, Amazon already have came out saying that VENOM has never affected their implementation of Xen, if Digital Ocean and Rackspace come out with the same statement it just makes this whole "bigger than HB stance" is silly.
And as far as the corporate/enterprise world goes, well VMware, CISCO, and MSFT hypervisors have a much bigger share out there and their hypervisors are not affected so again no much of a bite there.
is your argument that awareness of this issue would have been better if there wasn't a cool name and website?
VIRTUALIZED ENVIRONMENT NEGLECTED OPERATIONS MANIPULATION VENOM seriously, kinda reminds me of:
Ward: Strategic Homeland Intervention, Enforcement and Logistics Division.
Hill: And what does that mean to you?
Ward: It means someone really wanted our initials to spell out "SHIELD."
At least heartbleed and shellshock were kinda properly named, this one is a hell of a stretch.
Inb4 people start registering silly domains that can be used to spell out vulnerabilities.
CITRUS: Channel Insecure Transport Releases User Sessions
TBONE: Transmission Buffer Overflow Network Exploitation
BUTTER: Buffer Underrun Transactional Execution Relay
Let the parking wars begin!
BONECRUSH: Buffer Overrun Neatly Exceeds Current Reusable User Storage Hindrances
FACENEEDLE: Foreign Actors Can Execute Nefarious Executables, Even During Lockdown... Exploit
HELLSCREAM: Hack Exploiting Lazy Loading Standard Core Runtime Executables And Modules