Broadcom Fails to Disclose Zero-Day Exploitation of Vmware Vulnerability
Posted3 months agoActive3 months ago
securityweek.comTechstory
heatednegative
Debate
70/100
Vmware VulnerabilityBroadcomCybersecurity
Key topics
Vmware Vulnerability
Broadcom
Cybersecurity
Broadcom is criticized for failing to disclose a zero-day exploitation of a VMware vulnerability, with commenters expressing frustration over the company's handling of the issue and its impact on users.
Snapshot generated from the HN discussion
Discussion Activity
Light discussionFirst comment
37m
Peak period
3
3-4h
Avg / period
1.8
Key moments
- 01Story posted
Oct 1, 2025 at 8:41 AM EDT
3 months ago
Step 01 - 02First comment
Oct 1, 2025 at 9:18 AM EDT
37m after posting
Step 02 - 03Peak activity
3 comments in 3-4h
Hottest window of the conversation
Step 03 - 04Latest activity
Oct 1, 2025 at 12:56 PM EDT
3 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45437003Type: storyLast synced: 11/20/2025, 2:43:43 PM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
A cherry on the top: you need to pass a quest of registrations and approvals before you ever be able to have an opportunity to get access to any VMware software download. Good luck updating your software, folks.
They are but this a shit ton of money to be earned while doing so. VMWare is so cemented at companies that migration for many is going to be almost impossible.
>pre-1990's IBM that locked everything up into service contracts top to bottom
IBM still has a ton of those service contracts. It's small amount of their overall revenue but it's not nothing. 10 years from now, big F500 will still be on VMware paying insane amounts of money.
I was able to get to a download page for the latest version after making an account and traversing some confusing stuff, but it did want my real name and address before it would give me the download.
Not that containerization should be your only protection either, but generally I prefer random users not to have opportunity to just create and run arbitrary executables in default namespace.
This may explain the failure to notify of a 0day, since it seemed to be exploited accidentally in the course of a more sophisticated operation.
But that doesn’t excuse the lack of disclosure IMO. If it’s so trivial you could accidentally exploit it, seems bad.