Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-41106PUBLISHED: 2021-09-28
JWT is a library to work with JSON Web Token and JSON Web Signature. Prior to versions 3.4.6, 4.0.4, and 4.1.5, users of HMAC-based algorithms (HS256, HS384, and HS512) combined with `Lcobucci\JWT\Signer\Key\LocalFileReference` as key are having their tokens issued/validated using the file path as h...
CVE-2021-21522PUBLISHED: 2021-09-28Dell BIOS contains a Credentials Management issue. A local authenticated malicious user may potentially exploit this vulnerability to gain access to sensitive information on an NVMe storage by resetting the BIOS password on the system via the Manageability Interface.
CVE-2021-21569PUBLISHED: 2021-09-28Dell NetWorker, versions 18.x and 19.x contain a Path traversal vulnerability. A NetWorker server user with remote access to NetWorker clients may potentially exploit this vulnerability and gain access to unauthorized information.
CVE-2021-21570PUBLISHED: 2021-09-28Dell NetWorker, versions 18.x and 19.x contain an Information disclosure vulnerability. A NetWorker server user with remote access to NetWorker clients may potentially exploit this vulnerability and gain access to unauthorized information.
CVE-2021-36283PUBLISHED: 2021-09-28Dell BIOS contains an improper input validation vulnerability. A local authenticated malicious user may potentially exploit this vulnerability by using an SMI to gain arbitrary code execution in SMRAM.
Enterprise Cybersecurity Plans in a Post-Pandemic WorldDownload the Enterprise Cybersecurity Plans in a Post-Pandemic World report to understand how security leaders are maintaining pace with pandemic-related challenges, and where there is room for improvement.
Incident Readiness and Building Response Playbook
In this special report, learn the Xs and Os of any good security incident readiness and response playbook.
Tweet This
0 Comments
User Rank: Ninja
6/27/2019 | 2:10:54 PM
I agree with this assertion, look at what we are doing (US):
I mean at some point, we had to know that they were going to reverse engineer this virus and unleash a Cyber-Apocalypse on the US. I am not so sure if our utility infrastructrure will be able to handle it . Also, remember, they have tried this already with Triton, thankfully this was thwarted most recently https://ubm.io/2IFcbA0 (Triton Attack). This is what "FireEye" said about the attack - https://www.fireeye.com/blog/threat-research/2017/12/attackers-deploy-new-ics-attack-framework-triton.html
The TRITON malware contained the capability to communicate with Triconex SIS controllers (e.g. send specific commands such as halt or read its memory content) and remotely reprogram them with an attacker-defined payload. The TRITON sample Mandiant analyzed added an attacker-provided program to the execution table of the Triconex controller. This sample left legitimate programs in place, expecting the controller to continue operating without a fault or exception. If the controller failed, TRITON would attempt to return it to a running state. If the controller did not recover within a defined time window, this sample would overwrite the malicious program with invalid data to cover its tracks.
This sounds very similar to Stuxnet (we made this), we need to initiate a "a stand-down" order on the attacks we are initiating from the US to other OCONUS locations or this situation will only get worse. A word to the wise, I think we have been warned enough and we continue to play with fire.