Cybercriminals are scanning servers for the Microsoft Exchange ProxyShell RCE vulnerabilities after technical details presented at the Black Hat

Taiwanese motherboard maker Gigabyte has been hit by the RansomEXX ransomware gang, who threaten to publish 112GB of stolen data unless a ransom is paid. Gigabyte is best known for its motherboards, but also manufactures other computer components and hardware, such as graphics cards, data center servers, laptops, and monitors. The attack occurred late Tuesday…

Governance & Risk Management , IT Risk Management , Patch Management Fancy Product Designer Flaw Allows Remote Code Execution Akshaya Asokan (asokan_akshaya) • June 2, 2021     Users are advised to uninstall the Fancy Product Designer plug-in. (Image: Fancy Product Design) Hackers are exploiting a critical zero-day flaw in the WordPress plug-in Fancy Product…

Microsoft on Friday warned of active attacks exploiting unpatched Exchange Servers carried out by multiple threat actors, as the hacking campaign is believed to have infected tens of thousands of businesses, government entities in the U.S., Asia, and Europe. The company said “it continues to see increased use of these vulnerabilities in attacks targeting unpatched…

Fraud Management & Cybercrime , Incident & Breach Response , Ransomware Extortionists Demand $50 Million – Payable in Monero Cryptocurrency – From Oil Giant Scott Ferguson (Ferguson_Writes) • July 22, 2021     Saudi Aramco’s gas processing plant in Khursaniyah, Saudi Arabia (Photo: Saudi Aramco) Saudi Aramco, one of the world’s largest oil and natural…

2020 was a year of relentless disruptions. The protective layer of secured enterprise networks and controlled IT environments of the physical premises did not exist. Over the past year, CISOs (Chief Information Security Officers) have had to grapple with the challenges of bolstering the security posture, minimizing risks, and ensuring business continuity in the new…

An information disclosure vulnerability exists in the /proc/pid/syscall functionality of Linux Kernel 5.1 Stable and 5.4.66. More specifically, this issue has been introduced in v5.1-rc4 (commit 631b7abacd02b88f4b0795c08b54ad4fc3e7c7c0) and is still present in v5.10-rc4, so it�s likely that all versions in between are affected.