Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-2289PUBLISHED: 2022-07-03Use After Free in GitHub repository vim/vim prior to 9.0.
CVE-2022-2288PUBLISHED: 2022-07-03Out-of-bounds Write in GitHub repository vim/vim prior to 9.0.
CVE-2022-2290PUBLISHED: 2022-07-03Cross-site Scripting (XSS) - Reflected in GitHub repository zadam/trilium prior to 0.52.4, 0.53.1-beta.
CVE-2022-2287PUBLISHED: 2022-07-02Out-of-bounds Read in GitHub repository vim/vim prior to 9.0.
CVE-2022-34911PUBLISHED: 2022-07-02
An issue was discovered in MediaWiki before 1.35.7, 1.36.x and 1.37.x before 1.37.3, and 1.38.x before 1.38.1. XSS can occur in configurations that allow a JavaScript payload in a username. After account creation, when it sets the page title to "Welcome" followed by the username, the usern...
User Rank: Apprentice
11/30/2017 | 11:14:16 PM
Understand that it's critical to understand what went wrong to cause the incident, but I feel it would be very insightful to understand who made the decision not to disclose the incident.
Where did that decision occur? At Uber's Board, CEO, Legal team. Even if that decision was left to the CISO then that's actually a damning indictment on their delegation of authority.
I understand that Uber want to offer up the CISO as the official 'scapegoat' but wow if the standard response to a major data breach is 'sack the CISO' then in not to long we will be faced with an understaffed industry having to fill strategic leadership positions potentially with highly skilled cyber security people that may not have had the training and experience to work at the strategic C suite level.
Jason