Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Comments
Malicious PowerShell Use, Attacks on Office 365 Accounts Surged in Q4
Newest First  |  Oldest First  |  Threaded View
tdsan
tdsan,
User Rank: Ninja
4/15/2021 | 5:48:17 PM
Powershell and Windows 10 has numerous restrictive capabilities
If the user did not want to allow PowerShell (PS) scripts from running (especially from a Web or email server), then why not add lines like the following:
  • $exec = get-executionpolicy ; if ($exec -eq "Bypass" -or $exec -eq "Unrestricted") { set-executionpolicy -executionpolicy "Restricted"}
  • Run "Get-ExecutionPolicy" again just to make sure it is set to "Restricted"

In addition, all ports (if web-server) should be blocked, except port 443 or 80 in some respects (Windows firewall can do that but there are ofcourse better options - PaloAlto is a good one that we use), not sure why the execution policy (if configured properly) would even allow remove exploits like this to penetrate the initial defenses).

  • netsh advfirewall firewall add rule name="Require Encryption for Inbound TCP/80" protocol=TCP dir=in localport=80 security=authdynenc action=allow

I would also go to "taskschd.msc" and look at the "Task Scheduler Library" to ensure there are no running "PS" scripts. The user can create a script to run to ensure the setting is always set to "Restricted"
  • schtasks /create /TN restrict /SC Daily /TR "powershell -c restrict.ps1" /ST 06:00

This ensures the system is set to restrict executionpolicy or set it to Restricted.

Also, Windows 10 uses Windows Defender Security Center to protect against these types of Attacks, this could have been overlookewell, lessons learned.

Todd



Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Improving Enterprise Cybersecurity With XDR
Enterprises are looking at eXtended Detection and Response technologies to improve their abilities to detect, and respond to, threats. While endpoint detection and response is not new to enterprise security, organizations have to improve network visibility, expand data collection and expand threat hunting capabilites if they want their XDR deployments to succeed. This issue of Tech Insights also includes: a market overview for XDR from Omdia, questions to ask before deploying XDR, and an XDR primer.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-33085
PUBLISHED: 2022-06-30
ESPCMS P8 was discovered to contain an authenticated remote code execution (RCE) vulnerability via the fetch_filename function at \espcms_public\espcms_templates\ESPCMS_Templates.
CVE-2022-33087
PUBLISHED: 2022-06-30
A stack overflow in the function DM_ In fillobjbystr() of TP-Link Archer C50&A5(US)_V5_200407 allows attackers to cause a Denial of Service (DoS) via a crafted HTTP request.
CVE-2022-31115
PUBLISHED: 2022-06-30
opensearch-ruby is a community-driven, open source fork of elasticsearch-ruby. In versions prior to 2.0.1 the ruby `YAML.load` function was used instead of `YAML.safe_load`. As a result opensearch-ruby 2.0.0 and prior can lead to unsafe deserialization using YAML.load if the response is of type YAML...
CVE-2022-33082
PUBLISHED: 2022-06-30
An issue in the AST parser (ast/compile.go) of Open Policy Agent v0.10.2 allows attackers to cause a Denial of Service (DoS) via a crafted input.
CVE-2013-5683
PUBLISHED: 2022-06-30
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues during 2013. Notes: none.