CISA Adds Ivanti Cloud Services Appliance Vulnerability to Known Exploited Vulnerabilities Catalog (CVE-2024-8190)

Overview 

The Cybersecurity and Infrastructure Security Agency (CISA) has recently included a security flaw in Ivanti Cloud Services Appliance (CSA) in its Known Exploited Vulnerabilities (KEV) catalog. This newly cataloged vulnerability, identified as CVE-2024-8190, involves an OS command injection that poses a serious risk to affected systems.  

The vulnerability in question affects the Ivanti Cloud Services Appliance (CSA) version 4.6, specifically in all versions before Patch 519. It allows remote authenticated attackers with administrative privileges to execute arbitrary commands. This OS command injection flaw poses a risk as it can potentially lead to full system compromise. 

The vulnerability was assigned a CVSS score of 7.2, indicating a high severity level. Users of Ivanti CSA 4.6 must be aware of this issue and take appropriate action to mitigate the risk. 

Moreover, Cyble’s investigation revealed over 1,200 Ivanti CSA instances exposed on the internet, with a large number located in the United States. Systems using dual-homed configurations, with ETH-0 designated as an internal network, are less vulnerable to exploitation. 

Ivanti’s Response and Fixes 

Ivanti has recently released a critical patch to address this vulnerability. CVE-2024-8190 affects the Ivanti Cloud Services Appliance (CSA) version 4.6, specifically in all versions before Patch 519, allowing remote authenticated attackers to execute arbitrary commands. To mitigate this risk, Ivanti strongly recommends upgrading to CSA version 5.0, which includes the latest security improvements and ongoing support. 

For users who still need to transition to CSA 5.0, upgrading to CSA 4.6 Patch 519 is advised as an interim measure. However, CSA 4.6 has reached its end-of-life and will not receive future updates, making the upgrade to CSA 5.0 essential for continued security and support. 
 

Conclusion 

The addition of CVE-2024-8190 to CISA’s KEV catalog highlights the urgent need for organizations using Ivanti Cloud Services Appliance to address this vulnerability. With a known history of targeted cyber attacks on Ivanti products, organizations must apply the necessary patches and strengthen their security measures to prevent potential exploitation.  

Recommendations and Mitigations 


Move to this version for essential security updates and ongoing support. 

If an immediate upgrade to CSA 5.0 is not possible, update CSA 4.6 to Patch 519 as a temporary measure. 

Review and tighten administrative access controls to reduce the risk of exploitation. 

Increase surveillance for unusual or unauthorized activities and potential exploitation attempts. 

Develop a comprehensive patch management strategy, including regular updates and verification processes. 

Ensure critical systems are properly segmented and not directly exposed to the internet. 

The post CISA Adds Ivanti Cloud Services Appliance Vulnerability to Known Exploited Vulnerabilities Catalog (CVE-2024-8190) appeared first on Cyble.

Blog – Cyble – ​Read More

Top Cyber Threats of the Week: Brute Force Attacks, CVE Attempts and Malware Infections

Overview 

The Cyble Global Sensor Intelligence Network, or CGSI, has been actively monitoring and capturing real-time attack data through various Honeypot sensors. Last week’s research reveals the top cyber threats of the week including multiple exploit attempts, malware intrusions, financial fraud, and brute-force attacks. Multiple CVE attempts and targeted malware cases were observed from September 4, 2024, to September 10, 2024.  

CGSI’s recent research highlights a range of vulnerabilities impacting various IoT devices and software systems. A significant issue identified is the arbitrary code execution vulnerability in SPIP’s Porte Plume plugin, tracked as CVE-2024-7954. This flaw affects versions before 4.30-alpha2, 4.2.13, and 4.1.16, allowing attackers to execute arbitrary PHP code via specially crafted HTTP requests. Users are advised to upgrade to the latest patched versions to mitigate this risk. 

Another critical vulnerability is CVE-2024-4577, which involves PHP CGI configurations. This flaw permits attackers to execute arbitrary commands through malicious URL parameters. GeoServer versions prior to 2.23.6, 2.24.4, and 2.25.2 are affected by CVE-2024-36401, a remote code execution vulnerability due to unsafe XPath evaluation of OGC request parameters. Users should either apply the available patches or remove the vulnerable gt-complex library to secure their systems. 

CVE-2024-32113, a path traversal vulnerability in Apache OFBiz affecting versions before 18.12.13, was also a highlight of this week’s research. This flaw allows unauthorized access to restricted directories, making it essential for users to upgrade to version 18.12.13 to close this security gap. In SolarWinds Web Help Desk, CVE-2024-28987 exposes a hardcoded credential vulnerability that enables remote attackers to gain internal access and manipulate data.  

Brute Force Attacks and Malware Infections 

Brute-force attacks targeting IT automation software and databases have surged. These attacks are characterized by relentless attempts to decipher passwords and gain unauthorized access. They are particularly concerning due to their focus on critical infrastructure, which can lead to substantial disruptions and data breaches.  

These attacks have been significant, involving systematic attempts to guess passwords for unauthorized access. Notable volumes of these attacks have been observed, particularly against IT automation software and databases. Brute-force attacks consist of an attacker submitting many passwords or passphrases with the hope of eventually guessing a combination correctly.  

The attacker employs a systematic trial-and-error approach to test every possible password and passphrase until the correct one is discovered. This brute force attack method involves iteratively guessing login credentials or encryption keys and potentially accessing hidden web pages. Hackers methodically work through all possible combinations in hopes of success. Last week, Cyble recorded numerous such attacks, and the statistics related to specific source IPs are illustrated below (Figure 1). 

Figure 1 – Statistics of recent brute force attacks 

The figure below highlights the most frequently targeted usernames and passwords in brute-force attacks. The analysis shows that these attacks predominantly affect IT automation software and servers, such as “3comcso,” “elasticsearch,” and “hadoop,” as well as databases like “mysql” and “Postgres.” The most commonly used username/password combinations include “root,” “admin,” “password,” and “123456.”  

Figure 2 – Most used usernames and passwords 

Several case studies highlight ongoing threats in terms of malware attacks. The CoinMiner Linux Trojan targets Linux systems to use their resources for cryptocurrency mining, leading to significant performance degradation.  

The Linux Mirai malware attack utilizes the Mirai Botnet to exploit IoT devices and Linux servers for widespread network assaults. The Mirai Botnet is well-known for targeting these devices, converting them into remotely controlled bots that participate in extensive network attacks. 

Similarly, the Linux IRCBot attack leverages IRC connections to take control of compromised systems, frequently incorporating them into a botnet. These IRC connections serve as backdoors, enabling attackers to execute a range of actions on the compromised systems. Many of these systems are subsequently used as part of a botnet controlled through IRC. 

The Rise of Phishing Emails and Other Scams 

Phishing email attacks have been notably prevalent, with several new types of scams emerging recently, leveraging phishing and social engineering. One prevalent type of fraud is the Delivery Scam, where scammers impersonate courier officials to deceive victims into believing they have a package awaiting delivery. Victims are instructed to send sensitive personal details to a specified email address to receive the supposed delivery. These fraudulent emails often come from typo-squatted domains mimicking legitimate courier services.  

Another common phishing attack vector is the Project Funding Scam. In this scam, fraudsters promise victims a large sum of money for a project, tricking them into providing sensitive financial information under the pretense of transferring funds. An example seen in this scam involved an email purporting to be from the “World Bank Group”. 

The Relief Fund Scam is also prevalent. Scammers promise victims a substantial amount of money in exchange for a small upfront payment. The scam often masquerades as an email from a reputable organization, such as the “United Nations Compensation Committee Office,” using similar-looking email addresses.  

In 2024, QR code phishing attacks have surged, reflecting a growing trend among cybercriminals to exploit QR codes for malicious purposes. The rise in QR code phishing can be attributed to several factors.  

The widespread adoption of QR codes, particularly during the COVID-19 pandemic, has made them a convenient target for cybercriminals. Users are now more accustomed to scanning QR codes, which creates a false sense of security. QR codes also obscure the destination URL, making it difficult for users to verify the legitimacy of the site they are directed to. 

Previously, Cyble Research and Intelligence Labs (CRIL) identified a campaign targeting individuals in China. This campaign used Microsoft Word documents containing QR codes, which were distributed via spam email attachments and pretended to be from the Ministry of Human Resources and Social Security of China. The documents falsely offered labor subsidies and directed users to scan QR codes for authentication. These QR codes led to phishing sites designed to collect financial information, including credit card details and passwords. 

The phishing sites associated with this campaign used domains generated by a Domain Generation Algorithm (DGA) and were linked to a series of subdomains and IP addresses. The phishing sites prompted users to enter personal and financial information under the guise of claiming labor subsidies, ultimately aiming to facilitate unauthorized transactions. 

Conclusion 

The data gathered by the Cyble Global Sensor Intelligence (CGSI) network highlights a surge in cyber threats, including intensified brute-force attacks, critical vulnerabilities, and phishing scams. Key issues include vulnerabilities in SPIP’s Porte Plume plugin and PHP configurations, alongside malware attacks like CoinMiner and Mirai Botnet. Phishing scams, including QR code-based attacks, are increasingly targeting users.  

To mitigate these threats, organizations should promptly address vulnerabilities, implement strong passwords, block malicious IPs, and stay vigilant against phishing tactics. Regular updates and proactive security measures are crucial for protecting systems and data. 

Mitigations and Recommendations  


Ensure that your security systems block the hashes, URLs, and email addresses provided in the IoC list attachment. 

Address all listed vulnerabilities promptly and maintain vigilance by regularly monitoring top Suricata alerts within your internal networks. 

Consistently review the real-time attack table for any malicious ASNs and IP addresses. 

Implement measures to block IP addresses associated with brute-force attacks and secure the specific ports outlined in the IoC table. 

Immediately update default usernames and passwords to defend against brute-force attacks and establish a policy for regular password changes. 

Configure servers with complex, hard-to-guess passwords to enhance security. 

The post Top Cyber Threats of the Week: Brute Force Attacks, CVE Attempts and Malware Infections appeared first on Cyble.

Blog – Cyble – ​Read More

GitLab Community and Enterprise Editions Receive New Updates to Mitigate Severe Security Risks 

GitLab has rolled out essential patch updates for both its Community Edition (CE) and Enterprise Edition (EE), targeting multiple security vulnerabilities and system bugs. These critical updates are crucial for addressing high-severity issues that could jeopardize the security and functionality of GitLab environments.  

The new releases—versions 17.3.2, 17.2.5, and 17.1.7—introduce a range of fixes and improvements designed to counteract various vulnerabilities. Users operating on the affected versions are urged to promptly upgrade their GitLab instances to protect against these vulnerabilities.  

Cyble’s latest security advisory provides an in-depth examination of recent critical patches released by various vendors, with a particular focus on vulnerabilities addressed in GitLab. As a comprehensive DevOps platform, GitLab integrates the entire software development lifecycle into a single application, streamlining collaboration, code management, and deployment.  

Detailed Vulnerability Analysis 

The vulnerabilities identified in GitLab vary widely in severity, with CVSS base scores ranging from 3.1 to 9.9. These vulnerabilities encompass a range of critical issues, from unauthorized access to sensitive information to potential system compromises. Understanding and addressing these vulnerabilities is crucial for maintaining the security and integrity of GitLab installations. The following sections detail each vulnerability, including its severity, affected versions, and recommended remediation steps. 

Pipeline Execution as Arbitrary User (CVE-2024-6678) 

CVE-2024-6678, which carries a CVSS score of 9.9, represents a critical vulnerability affecting GitLab Community Edition (CE) and Enterprise Edition (EE) versions from 8.14 up to, but not including, 17.1.7, 17.2 up to 17.2.5, and 17.3 up to 17.3.2. This flaw allows attackers to trigger a pipeline as an arbitrary user under specific conditions. The impact of this vulnerability is severe, as it can lead to unauthorized actions within the GitLab environment. Cyble ODIN’s investigation has uncovered 89,706 internet-exposed GitLab instances, with a significant number located in China, highlighting the urgency of addressing this issue. 

Command Injection (CVE-2024-8640) 

CVE-2024-8640 is a high-severity vulnerability with a CVSS score of 8.5, affecting GitLab EE versions from 16.11 up to 17.1.7, 17.2 up to 17.2.5, and 17.3 up to 17.3.2. This issue allows for command injection into a connected Cube server due to incomplete input filtering. The potential consequences include unauthorized command execution, which could compromise the integrity and security of the affected systems. 

Server-Side Request Forgery (CVE-2024-8635) 

CVE-2024-8635, with a CVSS score of 7.7, affects GitLab EE versions from 16.8 up to 17.1.7, 17.2 up to 17.2.5, and 17.3 up to 17.3.2. This vulnerability enables server-side request forgery, allowing attackers to make requests to internal resources using a custom Maven Dependency Proxy URL. This flaw could potentially lead to unauthorized access to internal systems, increasing the risk of data exposure or other security breaches. 

Denial of Service (CVE-2024-8124) 

CVE-2024-8124, rated 7.5 on the CVSS scale, impacts GitLab CE/EE versions from 16.4 to 17.1.7, 17.2 to 17.2.5, and 17.3 to 17.3.2. This vulnerability could open the door for a denial of service attack by sending a large ‘glm_source’ parameter without requiring user interaction. The result can be a disruption of service availability, affecting users’ ability to access or utilize GitLab functionalities effectively. 

Improper Session Handling (CVE-2024-8641) 

With a CVSS score of 6.7, CVE-2024-8641 affects GitLab CE/EE versions from 13.7 to 17.1.7, 17.2 to 17.2.5, and 17.3 to 17.3.2. This vulnerability involves improper session handling, allowing an attacker with access to a victim’s CI_JOB_TOKEN to obtain the victim’s GitLab session token. There’s a high chance that this could potentially lead to unauthorized access to sensitive areas within the GitLab environment. 

Security Bypass (CVE-2024-8311) 

CVE-2024-8311, with a CVSS score of 6.5, is present in GitLab EE versions from 17.2 up to 17.2.5 and 17.3 up to 17.3.2. This flaw allows authenticated users to bypass pipeline execution policies by including a CI/CD template, potentially leading to unauthorized modifications or access within the GitLab pipeline. 

Information Disclosure (CVE-2024-4660) 

CVE-2024-4660, also rated 6.5 on the CVSS scale, affects GitLab EE versions from 11.2 up to 17.1.7, 17.2 up to 17.2.5, and 17.3 up to 17.3.2. This vulnerability permits guests to read the source code of private projects through group templates, leading to unauthorized information disclosure and potential security risks. 

Several other vulnerabilities, including CVE-2024-4283 and CVE-2024-4612, present medium-severity risks, such as open redirects and improper input validation. If not promptly addressed, these issues can lead to account takeovers, exposure of sensitive data, or unauthorized access.  

Each of these vulnerabilities has been assigned a CVSS score reflecting its impact and severity, and organizations are urged to apply relevant patches and updates. 

Conclusion 

Given GitLab’s critical role in many organizations’ software development processes, the recent updates addressing multiple vulnerabilities are of paramount importance. These vulnerabilities, ranging from unauthorized access and sensitive data exposure to potential denial of service attacks, could significantly impact an organization’s security and operational integrity. Organizations must apply the latest patches and updates to reduce any potential impact of these risks being exploited and improve their overall security posture. 

Recommendations and Mitigations 


Organizations are strongly advised to immediately upgrade to the latest GitLab versions where these vulnerabilities have been addressed. 

Properly configuring permissions and access levels should be a priority for firms that want to safeguard sensitive information. 

Regular monitoring of logs and auditing access can help detect unusual activities and potential exploitation attempts. 

Training users to recognize phishing attempts and secure their accounts will further mitigate risks associated with social engineering attacks. 

Implementing robust security policies, including multi-factor authentication (MFA) and regular security assessments, is crucial. 

Maintaining up-to-date backups and testing recovery procedures will ensure timely and rapid restoration in the aftermath of a security incident. 

It is recommended that a comprehensive patch management strategy be developed that includes inventory management, patch assessment, testing, deployment, and verification. 

Proper network segmentation to avoid exposure of critical assets over the Internet and maintaining an up-to-date inventory of all internal and external assets will further enhance organizational security. 

The post GitLab Community and Enterprise Editions Receive New Updates to Mitigate Severe Security Risks  appeared first on Cyble.

Blog – Cyble – ​Read More

CosmicBeetle joins the ranks of RansomHub affiliates – Week in security with Tony Anscombe

ESET research also finds that CosmicBeetle attempts to exploit the notoriety of the LockBit ransomware gang to advance its own ends

WeLiveSecurity – ​Read More

Stealthy Fileless Attack Targets Attendees of Upcoming US-Taiwan Defense Industry Event

Key Takeaways


Cyble Research and Intelligence Labs (CRIL) identified a campaign targeting individuals connected to the upcoming US-Taiwan Defense Industry Conference, as indicated by the lure document uncovered during the investigation.

The campaign involves a ZIP archive containing an LNK file that mimics a legitimate PDF registration form for deception.

When the LNK file is opened, it executes commands to drop a lure PDF and an executable in the startup folder, establishing persistence.

Upon system reboot, the executable downloads additional content and executes it directly in memory, effectively evading detection by the security products.

The first-stage loader triggers a second-stage loader, which downloads, decodes, and compiles C# code in memory, avoiding the creation of traceable files on disk.

Once the compiled code is executed, the malware exfiltrates sensitive data back to the attacker’s server via web requests designed to blend in with normal traffic, making detection more difficult.

Overview

The initial infection vector of this campaign remains unclear; however, based on the lure document analyzed, there are indications that the attack may have been delivered to users via spam emails. The attack commences with a suspicious archive file containing an LNK file disguised as a PDF document. This deception is designed to trick users into executing the malicious LNK file, which in turn triggers a series of covert actions in the background.

Upon execution, the LNK file extracts two components: a base64-encoded executable and the actual lure PDF. The executable is protected using .NET’s Confuser, an obfuscation tool, to evade detection and is placed in the startup folder to ensure persistence on the compromised system. Once the executable runs, it retrieves additional malicious content, specifically a DLL file, from a remote server. This DLL file is Encrypted using XOR operation to further obscure its purpose.

The executable employs .NET’s “Assembly.Load” function to load the decrypted DLL directly into memory, enabling it to bypass traditional security mechanisms that scan files written to disk. After the DLL is loaded, it downloads encrypted C# code from the TA-controlled server, compiles it on the victim’s machine, and then executes it entirely in memory.

During our testing of this malware, we were unable to capture the final payload. However, analysis of the loader’s code suggests that the payload’s ultimate purpose is to exfiltrate sensitive data from the victim’s machine to conduct further malicious activities. Based on the lure document used in this attack, it is likely that the TA behind this campaign is specifically targeting individuals associated with the upcoming US-Taiwan Defense Industry Conference.

The figure below shows the infection chain.

Technical Analysis

CRIL uncovered a campaign targeting users by posing as registration forms for the upcoming Conference and distributed malicious ZIP files under the name “registration_form.pdf.zip”. The ZIP file contains an LNK file disguised as a PDF. When extracted, the archive presents a file named “registration_form.pdf,” but this is actually an LNK file with a dual extension (.pdf.lnk), misleading the user into thinking it is a legitimate PDF document. The malicious LNK file contains an embedded executable and a lure PDF, both encoded in base64 format, further concealing the malicious content, as shown in Figure 2.

When the user opens the LNK file, it triggers several background commands. First, the LNK file searches the base64 embedded content using the “findstr” command and saving them as “1.txt” and “2.txt,” respectively. Next, the “certutil” utility decodes these files, storing the lure PDF as ” registration_form.pdf ” in the Temp directory and the executable as “update.exe” in the “%AppData%RoamingMicrosoftWindowsStart MenuProgramsStartup” folder, ensuring persistence. Finally, the registration_form.pdf is opened with the system’s default PDF viewer. The figure below shows the content of the malicious LNK file.

Lure Document:

The lure document used in this attack suggests that the TA behind the campaign is likely targeting individuals connected to the upcoming US-Taiwan Defense Industry Conference, which is scheduled to take place in the United States from September 22nd to September 24th, 2024.

The potential targets are expected to include key participants such as defense officials, industry executives, government representatives, and other stakeholders involved in or attending the event. The timing and focus of the campaign suggest that the TA aims to exploit the significance of the conference, potentially for gathering sensitive information to conduct further malicious activities. This strategic targeting underscores the sophisticated nature of the campaign and its alignment with geopolitical interests. The figure below shows the Lure document.

First Stage Loader: updater.exe

The “Updater.exe” file functions as a loader and is protected using the .NET “Confuser protector.” It is placed in the Startup folder, ensuring it executes each time the user logs into the system. Upon execution, the file first verifies if it is running from the “Startup” directory. If it is, the execution proceeds; otherwise, it terminates without further action. When the file runs, it sends a POST request to a compromised site controlled by the TA, transmitting the victim’s machine.

Next, using “WebClient”, it downloads string content from “hxxp://tdea.com.tw/asset/uploads/files/68679813[.]txt” and removes the first character to retrieve the correct base64-encoded content. This reveals the


machine name: “MSEDGEWIN10″

URL for the 2nd stage loader: “hxxp://tdea.com.tw/asset/uploads/files/68679815[.]txt

The first-stage loader downloads a base64-encoded data stream from the above URL, which is first decoded and then further processed by applying an XOR operation using a hardcoded key with a decimal value of 16. This operation results in the extraction of a DLL file. The below shows the decryption loop used for getting the DLL file.

The extracted DLL is then dynamically loaded and executed using the .NET “Assembly.Load” function, allowing the TA to invoke malicious functionality embedded within the DLL. The below figure shows how the “Assembly.Load” function is used to load the decrypted DLL and call a specific method named “MyEntry” with in a class named “ConsoleApp.MyClass

Second Stage Loader

The “.NET Assembly.Load” function is used to load the second-stage loader, which functions similarly to the initial stage. This DLL loader retrieves additional base64-encoded content from the TA’s controlled server. Once the content is downloaded, it is decoded using base64 and then processed with an XOR operation using a hardcoded key of 48 in decimal, as shown below.

Although the URL “hxxp://tdea.com.tw/asset/uploads/files/68679811[.]txt” currently doesn’t contain any data, code analysis indicates that the decoded content is likely XML data containing C# code and assembly references (DLLs) which utilizes “Compile After Delivery” technique to compile the source code during runtime.

In-memory Execution

The downloaded C# code is compiled in memory using specific compiler parameters such as “GenerateExecutable = false” and “GenerateInMemory = true”. These parameters, along with references to core assemblies like “System.dll”, “System.Data.dll”, and “System.Management.dll”. The “System.Management.dll” is specifically used to interact with Windows Management Instrumentation (WMI), allowing the code to query system properties and interact with system components through WMI queries. This suggests that the TA may use WMI queries to gather system information from the victim.  

Additional DLLs may also be included as reference assemblies. The compiled code is executed directly in memory, bypassing the disk entirely, which complicates detection by conventional security tools.

This method is highly effective for evasion. It allows malware or APT groups to dynamically generate and execute payloads at runtime, making detection and mitigation efforts significantly more challenging for defenders. The figure below shows a code snippet responsible for compiling the downloaded C# code and executing it in memory.

Data Exfiltration

After executing the compiled code, the resulting data is sent back to the TA’s server using a web request. A “WebClient” object is utilized to upload the data, where the request’s “ContentType” is set to “application/x-www-form-urlencoded” to simulate standard form data submission, and the “UserAgent” header is modified to mimic a web browser. The “UploadString” method is used to send a POST request to the TA’s specified URL, along with parameters such as a randomly generated filename, a command flag, and the encoded content being transmitted.

Network Communication:

The TA leverages a compromised website to host malicious content and frequently retrieves files stored within an exposed open directory. Moreover, the TA employs CKFinder, a PHP-based file management framework, to upload and manage files sent from the victim machines. This framework allows the TA to store exfiltrated data or additional malicious payloads on the server. The image below illustrates the structure of the open directory on the compromised site, highlighting the ease with which the TA can access and manipulate stored files.

Threat Attribution

Chinese threat actors have a well-documented history of targeting Taiwan, particularly around significant political events. For instance, during the period leading up to Taiwan’s presidential election earlier in 2024, there was a marked increase in cyberattacks within the 24 hours preceding the election, as reported by Trellix. This surge underscores China’s ongoing efforts in cyber espionage aimed at Taiwan’s political and military sectors. Despite this pattern, the specific TA behind the current campaign remains unidentified, and we have not been able to link these tactics, techniques, and procedures (TTPs) to any known threat actor or advanced persistent threat (APT) group at this time.

Conclusion

This sophisticated attack employs social engineering and advanced in-memory execution techniques to avoid detection. By disguising the LNK file as a legitimate conference registration PDF and executing payloads dynamically in memory, the TAs can conduct malicious activities to steal sensitive information without leaving traces on the disk. Given the timing and context of the US-Taiwan Defense Industry Conference, this campaign is likely intended to conduct malicious operations targeting valuable information related to defense collaborations.

Our Recommendations


Deploy advanced email filtering solutions to block phishing emails and suspicious attachments before they reach the end users. Anti-phishing solutions that use machine learning or behavior analysis can also identify and block malicious campaigns at an early stage.

Implement security solutions with advanced threat detection that can monitor in-memory execution of code or PowerShell commands. Tools like EDR (Endpoint Detection and Response) should be used to detect unusual behavior, such as programs compiling and running C# code in memory.

Ensure that users have the least privileges required for their roles, reducing the risk of malware being able to execute in privileged areas.

Application whitelisting or blocking untrusted applications from executing in certain directories can also minimize the risk.

Monitor outbound network traffic for signs of exfiltration and communication with command-and-control (C2) servers, especially encrypted and base64-encoded traffic. Use firewalls, IDS/IPS (Intrusion Detection and Prevention Systems), and network analysis tools to detect suspicious web traffic patterns.

MITRE ATT&CK® Techniques

Tactic
Technique
Procedure

Initial Access (TA0001)
Spearphishing Attachment (T1566.001)
The ZIP archive containing the LNK file may be delivered via phishing or spam emails

Persistence (TA0003)
Registry Run Keys / Startup Folder (T1547.001)
update.exe added into the Startup folder

Execution (TA0002)
User Execution: Malicious File  (T1204.002)
Malicious LNK file executed by the user after extracted from archive file

  Defence Evasion (TA0005)
Obfuscated Files or Information: LNK Icon Smuggling (T1027.012)
The LNK file uses a PDF file icon, leveraging the “IconEnviromentDataBlock” to appear as a harmless PDF document.

Defence Evasion (TA0005)
Deobfuscate/Decode Files or Information (T1140)  
Certutil is used to decode base64 content.

Defence Evasion (TA0005)
Obfuscated Files or Information: Compile After Delivery (T1027.004)
CSharp code is compiled and executed in memory

Command and Control (TA0011)
Data Encoding: Non-Standard Encoding (T1132.002)  
Encrypted file is downloaded from TA controlled server.

Exfiltration (TA0010)
Exfiltration Over Alternative Protocol: Exfiltration Over Unencrypted Non-C2 Protocol (T1048.003)  
Exfiltrated data is transmitted using standard protocol.

Indicators of Compromise (IOCs)

Indicator
Indicator Type
Comments

6b1af6be189e31168b8f4eff84cd475eb5d0cbd08e646760fb352165a30cb269
SHA-256
registration_form.pdf.zip

4989882339d745692eabe0a375d8cecd6e7e3af534cd1173d94867b8d069cd7f
SHA-256
registration_form.pdf.lnk

0e07b96c508dfc0e11f119071cca4ec628dae635771532dae7f034ed369591d7
SHA-256
updater.exe

df92e2c56f53c9139da70c5a813b6512df616abd56dc10dc80a625c4512cb7f2
SHA-256
updater.exe

e0174968064b45d1b0c255bec351de94bb59852cb7f2e6ac694debbac59acb7a
SHA-256
d.dll

5aaa5a7ef2eaa13e6e4274ccdb3c80251c868043fa51c2ca1e5b556a65d5166c              
SHA-256
68679815.txt

531db819d928243bda43997165da1fa3ebda3412e7d9928cb6bd2a8c898a85ae                       
SHA-256
68679813.txt

hxxp://tdea.com.tw/asset/uploads/files/68679813[.]txt
URL
URL used to get the DLL link

hxxp://tdea.com.tw/asset/uploads/files/68679815[.]txt
URL
URL used to get the DLL file

hxxp://tdea[.]com[.]tw/ckeditor/ckfinder/core/connector/php/connector[.]php?command=SaveFile&type=Files&currentFolder=%2F&langCode=en&hash=f92a86fd96382c5a

URL
POST request to send exfiltrated data

hxxp://tdea.com.tw/asset/uploads/files/68679811[.]txt
URL
URL used to get the CSharp (C#) code

The post Stealthy Fileless Attack Targets Attendees of Upcoming US-Taiwan Defense Industry Event appeared first on Cyble.

Blog – Cyble – ​Read More

Transatlantic Cable podcast episode 363 | Kaspersky official blog

Episode 363 kicks off with a discussion around moderation on the popular messaging service, Telegram. From there the team move to discuss how one person managed to siphon off over $10 million from the likes of Spotify and Apple using bots to stream music.

To wrap up the team discuss two stories, the first looking at how the Democrats in America are using “brain rot” videos, and the second looks at the seedy underworld of stolen mobile phones.

If you like what you heard, please consider subscribing.

Telegram reportedly ‘inundated’ with illegal and extremist activity
Musician charged with $10M streaming royalties fraud using AI and bots
Kamala Harris Campaign Experiments With Ads for an Audience With “Brain Rot”
Thieves snatched his phone in London – it was in China a month later

Kaspersky official blog – ​Read More

We can try to bridge the cybersecurity skills gap, but that doesn’t necessarily mean more jobs for defenders

I have written about the dreaded “cybersecurity skills gap” more times than I can remember in this newsletter, but I feel like it’s time to revisit this topic again.  

That’s because the White House announced a new initiative last week for the U.S. government called the “Service for America” initiative designed to train new workers in the cybersecurity field. This measure directs U.S. federal agencies to help recruit and prepare Americans for jobs in cybersecurity and AI by removing certain degree requirements and emphasizing skills-based hiring. This means, hopefully, more educational resources for people looking to break into cybersecurity. 

On its face, I’m all in favor of this. I did eventually go back to school to get my associate’s degree in cybersecurity, but much of what I’ve learned about this field has been from working at Talos and spending time around my talented and intelligent colleagues, many of whom did not go to college for cybersecurity.  

The U.S. government also has separate initiatives to support neurodivergent candidates who want to work in security, as well as those who are blind and visually impaired

My concern is that, even if we do train these employees and give them the proper skills, it’s on companies to eventually hire them.  

A June report from CyberSeek found that there are only enough skilled workers to fill 85 percent of cybersecurity jobs in America. Yet hiring in the industry has remained flat, according to a soon-to-be-released report from cybersecurity non-profit ISC2. This year, the global security workforce is estimated to be 5.5 million, which is only a 0.1 percent increase year over year, according to the report. 

Among the more than 15,000 cybersecurity practitioners from around the globe who responded to the study, 38 percent of respondents said their organizations had experienced a cybersecurity hiring freeze over the past year, up 8 percent from 2023. Thirty-seven percent of respondents reported budget cuts to the security program, and another 25 percent said their teams had experienced layoffs.  

That same CyberSeek report also found that, in the U.S., the amount of cybersecurity-related job postings decreased by 29 percent year-over-year. 

So as these skills gap-closing programs begin, we need to be thinking about what skills, exactly, managers want their workers to be trained in. There is obviously some sort of disconnect here between the people who want to work in security compared to the companies or managers who want to hire them. Or there just simply isn’t enough money to go around right now to handle staffing up cybersecurity teams, and that’s just the reality of the current economy in the U.S. and globally.  

I’m not saying this to discourage anyone from entering the security space or spread doom and gloom. But I do think it’s important to acknowledge that there are many already skilled and trained workers who simply cannot find work or are treading water throwing dozens of applications at the wall to see what sticks. 

I’ve seen too many people posting on LinkedIn recently looking for a cybersecurity job to think that the solution to bolstering security is getting *another* worker in with the same skillset to compete for the same job opening as someone who’s been in the industry for 10 years. 

The one big thing 

Talos recently uncovered a new threat called “DragonRank” that primarily targets countries in Asia — and a few in Europe — operating PlugX and BadIIS for search engine optimization (SEO) rank manipulation. DragonRank exploits targets’ web application services to deploy a web shell and utilizes it to collect system information and launch malware such as PlugX and BadIIS, running various credential-harvesting utilities. Their PlugX not only used familiar sideloading techniques, but the Windows Structured Exception Handling (SEH) mechanism ensures that the legitimate file can load the PlugX without raising suspicion. 

Why do I care? 

This group compromises Windows Internet Information Services (IIS) servers hosting corporate websites, with the intention of implanting the BadIIS malware. BadIIS is malware used to manipulate search engine crawlers and disrupt the SEO of the affected sites. With those compromised IIS servers, DragonRank can distribute the scam website to unsuspecting users. DragonRank engages in SEO manipulation by altering or exploiting search engine algorithms to improve a website’s ranking in search results. They conduct these attacks to drive traffic to malicious sites, increase the visibility of fraudulent content, or disrupt competitors by artificially inflating or deflating rankings. These attacks can harm a company’s online presence, lead to financial losses, and damage its reputation by associating the brand with deceptive or harmful practices. The actor then takes these compromised websites and promotes them, effectively turning these sites into platforms for scam operations. 

So now what? 

Talos released a new Snort rule set and several ClamAV signatures to detect and block the malware used in these attacks. Talos has confirmed more than 35 IIS servers had been compromised and deployed the BadIIS malware across a diverse array of geographic regions, including Thailand, India, Korea, Belgium, Netherlands and China in this campaign, so it’s clearly still active and potentially growing. 

Top security headlines of the week 

A new type of attack called “RAMBO” could allow adversaries to steal data over air-gapped networks with RAM radio signals. An Israeli academic researcher recently announced the discovery of RAMBO (Radiation of Air-gapped Memory Bus for Offense), in which an attacker could generate electromagnetic radiation from a device’s RAM to send data from air-gapped computers. Air-gapped systems are otherwise offline networks that are extremely isolated, often used in critical environments like government agencies, weapons systems and nuclear power stations. While RAMBO does not pose a threat for any hacker with access to the internet, it could open the door for insider threats with access to the network to deploy malware through physical media like USB drives or supply chain attacks. RAMBO could allow attackers to seal encoded files, encryption keys, images, keystrokes and biometric information from these systems at a rate of 1,000 bits per second. Researchers conducted tests into these types of attacks over distances of up to 23 feet. A technical paper published on the topic includes several potential mitigations, including RAM jamming, external EM jamming and Faraday enclosures around potentially targeted systems. (Bleeping Computer, SecurityWeek

Commercial spyware makers are still finding ways to bypass government sanctions and, in some cases, have made their tools harder to detect. A new report from the Atlantic Council found that “Most available evidence suggests that spyware sales are a present reality and likely to continue.” The report specifically highlights increased activity from Intellexa and the NSO Group, two companies known for creating and selling spyware tools that have been targeted over the past few years by international sanctions. These companies, and specifically Intellexa, have found ways to work around sanctions by restructuring their businesses with subsidiaries, partners and other relationships spread across multiple geographic areas. Intellexa is known for creating the Predator spyware, while the NSO Group is infamous for the Pegasus spyware. Both pieces of software often target high-risk individuals, sometimes by governments, such as journalists, politicians and activists. Security researchers also recently found that Intellexa has established new infrastructure in the Democratic Republic of the Congo and Angola, making “it more difficult for researchers and cybersecurity defenders to track the spread of Predator.” (Dark Reading, The Register

Several Western intelligence agencies have formally charged the Russian GRU for carrying out cyber attacks against Ukraine designed to disrupt aid efforts. Government agencies in the U.S., U.K. and several other countries blamed Unit 29155, which has been linked to past espionage campaigns, with targeting government and civilian agencies and civil society organizations in Western Europe, the EU and NATO after Russia invaded Ukraine in 2022. Intelligence agencies in the Netherlands, Czech Republic, Germany, Estonia, Latvia, Canada and Australia all signed the declaration. They also formally blamed Unit 29155 for the WhisperGate campaign, a coordinated attack on Ukrainian government agencies in January 2022 that seemed to set the stage for a physical ground invasion. The announcement stated that WhisperGate has since been used to “scout and disrupt” aid deliveries to Ukraine. When Talos first reported on WhisperGate in 2022, our researchers stated that “attackers used stolen credentials in the campaign and they likely had access to the victim network for months before the attack, a typical characteristic of sophisticated advanced persistent threat (APT) operations.” (Reuters, BBC

Can’t get enough Talos? 

The 2024 Threat Landscape State of Play Vulnerability in Tencent WeChat custom browser could lead to remote code execution Watch our new documentary, “The Light We Keep: A Project PowerUp Story” Vulnerability in Acrobat Reader could lead to remote code execution; Microsoft patches information disclosure issue in Windows API Four zero-days included in group of 79 vulnerabilities Microsoft discloses, including one with 9.8 severity score 

Upcoming events where you can find Talos 

LABScon (Sept. 18 – 21)  

Scottsdale, Arizona 

VB2024 (Oct. 2 – 4) 

Dublin, Ireland 

MITRE ATT&CKcon 5.0 (Oct. 22 – 23) 

McLean, Virginia and Virtual

Nicole Hoffman and James Nutland will provide a brief history of Akira ransomware and an overview of the Linux ransomware landscape. Then, morph into action as they take a technical deep dive into the latest Linux variant using the ATT&CK framework to uncover its techniques, tactics and procedures.

Most prevalent malware files from Talos telemetry over the past week 

SHA 256: 47ecaab5cd6b26fe18d9759a9392bce81ba379817c53a3a468fe9060a076f8ca 
MD5: 71fea034b422e4a17ebb06022532fdde 
Typical Filename: VID001.exe 
Claimed Product: N/A 
Detection Name: RF.Talos.80 

SHA 256: 3a2ea65faefdc64d83dd4c06ef617d6ac683f781c093008c8996277732d9bd66 
MD5: 8b84d61bf3ffec822e2daf4a3665308c 
Typical Filename: RemComSvc.exe 
Claimed Product: N/A 
Detection Name: W32.3A2EA65FAE-95.SBX.TG 

SHA 256: 35dcf857f0bb2ea75bf4582b67a2a72d7e21d96562b4c8a61b5d598bd2327c2c 
MD5: fab8aabfdabe44c9a1ffa779fda207db 
Typical Filename: ACenter.exe 
Claimed Product: Aranda AGENT 
Detection Name: Win.Trojan.Generic::tg.talos  

SHA 256: 0e2263d4f239a5c39960ffa6b6b688faa7fc3075e130fe0d4599d5b95ef20647 
MD5: bbcf7a68f4164a9f5f5cb2d9f30d9790 
Typical Filename: bbcf7a68f4164a9f5f5cb2d9f30d9790.vir 
Claimed Product: N/A 
Detection Name: Win.Dropper.Scar::1201 

SHA 256: 5e537dee6d7478cba56ebbcc7a695cae2609010a897d766ff578a4260c2ac9cf 
MD5: 2cfc15cb15acc1ff2b2da65c790d7551 
Typical Filename: rcx4d83.tmp 
Claimed Product: N/A   
Detection Name: Win.Dropper.Pykspa::tpd 

Cisco Talos Blog – ​Read More

ANY.RUN Now Integrates with Splunk!

We have some thrilling news to share with you today. Our team at ANY.RUN is happy to announce the launch of our new integration with Splunk!

How this integration benefits you 

Official page of ANY.RUN’s connector for Splunk

If you’re a Splunk user, you can now leverage ANY.RUN’s Interactive Sandbox and Threat Intelligence Lookup directly from your Splunk SOAR environment.  

This means that you can analyze potentially malicious files and URLs in the sandbox and enrich your investigations with threat data from TI Lookup without leaving the familiar Splunk interface.  

Our main goal with this integration is to give you more options and help you make the most out of ANY.RUN while working with familiar systems.  

The integration supports a wide range of actions, from simple reputation checks to full detonation and analysis of suspicious objects.  

Integrate ANY.RUN solutions in your organization 



Contact Sales


Key Features 

Comprehensive Threat Intelligence 

The integration allows analysts to query ANY.RUN’s threat intelligence database directly from Splunk SOAR. 

Use the get intelligence action to query TI Lookup’s database

Automated Malware Analysis 

One of the most powerful features of this integration is the ability to automatically detonate files and URLs in ANY.RUN’s sandbox.  

This process can be triggered as part of a Splunk SOAR playbook, allowing for analysis of attachments in phishing emails or suspicious downloads detected by network monitors. You can also access any analysis session you launch in the sandbox to perform manual actions or gain a deeper understanding of the threat.

You can perform file analysis, collect IOCs, get IP reputation, and more

Detailed Reporting and IOC Extraction 

The ‘get report’ action retrieves key analysis details, including the verdict on the sample’s threat level. You can also see the rest of the analysis results by navigating to the corresponding part of the interface.

The interface lets you quickly see the verdict on the sample

Advanced Threat Hunting 

If you have ANY.RUN’s TI License, you can use the ‘get intelligence’ action to perform complex queries against ANY.RUN’s threat intelligence database. 

Threat Intelligence Lookup lets you use dozens of search parameters

Search for specific file hashes, IP addresses, domains, or even MITRE ATT&CK techniques you uncover in previous analyses.

Real-World Application 

Consider a scenario where a Splunk SOAR playbook is triggered by a potential phishing email. 

The playbook could automatically extract any URLs and attachments from the email, then use the ‘url reputation’ action to check if the URLs have been previously analyzed by ANY.RUN. 

For new or suspicious URLs, the playbook could use the ‘detonate url’ action to analyze them in a sandbox environment. 

Similarly, for attachments, the ‘detonate file’ action could be used to safely execute and analyze them. 

The playbook could then retrieve detailed reports and IOCs using the ‘get report’ and ‘get iocs’ actions. 

Finally, it could use the extracted IOCs to automatically update firewall rules, trigger endpoint scans, or create new detection rules in the SIEM. 

Test all features of ANY.RUN
See how it can benefit your team 



Get FREE trial


How to Set it Up 

To leverage this new integration, users will need a Splunk SOAR environment and an ANY.RUN account with API access. Preferably, a ‘Hunter’ or ‘Enterprise’ subscription is recommended for full feature access. 

Splunk connector details

The setup process is straightforward: 

Configure a new ANY.RUN asset in Splunk SOAR.

Provide the ANY.RUN base URL (typically https://api.any.run).

Enter the API key from your ANY.RUN profile page.

Set a default timeout for API requests.

The connector is easy to set up

Once configured, the ANY.RUN actions will be available for use in Splunk SOAR playbooks and for manual invocation by analysts. 

About ANY.RUN  

ANY.RUN helps more than 400,000 cybersecurity professionals worldwide. Our interactive sandbox simplifies malware analysis of threats that target both Windows and Linux systems. Our threat intelligence products, TI Lookup, Yara Search and Feeds, help you find IOCs or files to learn more about the threats and respond to incidents faster.  

With ANY.RUN you can: 

Detect malware in seconds

Interact with samples in real time

Save time and money on sandbox setup and maintenance

Record and study all aspects of malware behavior

Collaborate with your team 

Scale as you need

Request free trial → 

The post ANY.RUN Now Integrates with Splunk! appeared first on ANY.RUN’s Cybersecurity Blog.

ANY.RUN’s Cybersecurity Blog – ​Read More

Alert notification as phishing bait | Kaspersky official blog

What would prompt someone to sign in to their work email account on the spot? That’s right, a warning about a hack. The first impulse of a responsible employee who receives such a security alert is to find out what happened, change their password, and maybe even notify others who may have been affected. But that knee-jerk reaction is in fact a reason NOT to act immediately, but rather take a deep breath and triple-check everything. Here’s why.

Phishing email

The email that kicks off this phishing attack we recently encountered pretends to be a notification from Office 365, and it does a pretty good job.

Sure, perfect it ain’t: the Microsoft logo is too big and looks odd without the company name; notifications of this kind usually have the Office 365 logo; and the alert itself is a bit muddled. In the second line, for example, it mentions that someone created a “forwarding/redirect rule”, but the “Details” line specifies that this alert was triggered because someone gained “access to read your user’s email”. These details will stand out to the user who gets a lot of Office 365 notifications – but most users don’t.

What should really catch even the untrained eye is the sender’s address. Genuine Office 365 notifications signed “The Office 365 Team” come from, yes, Microsoft’s email servers, not from an administrator on an unrelated domain.

The “Severity” line also looks odd: “Informational” notifications usually don’t require any user action.

DIY redirect

Concerned recipients scared into clicking the “View alert details” link are taken to a page that mimics a broken redirect.

In fact, a cursory check of the browser address bar, or even the name of the tab, clearly shows that this page is hosted in the Google Docs cloud. To be precise, it’s a single-slide presentation with a link. The purpose behind it is that the initial phishing email contains only a link to docs.google.com, which has a positive reputation in the eyes of most anti-phishing engines. Recipients are invited to follow the link because automating a redirect from a presentation slide is simply impossible, and the attackers need some way to lure them to the phishing site; the victim is asked to walk into the trap themselves.

These are all clear signs of phishing that you need to watch out for every time you follow a link in a corporate email. The finale isn’t hard to guess: a simple page for harvesting Office 365 credentials. The address gives it away, of course.

How to protect employees from phishing

We recommend regular training for employees in the art of spotting the latest cybercriminal tricks (for example, by showing them our posts dedicated to signs of phishing). It’s even better to use a dedicated platform to raise cybersecurity awareness throughout the company.

And to make extra sure, provide corporate users with multi-layered anti-phishing protection capable of both filtering out bulk emails at the mail gateway level and blocking redirects to dangerous web pages using security solutions on a workstation.

Kaspersky official blog – ​Read More

Major ICS Security Flaws Disclosed in LOYTEC, Hughes, and Baxter Products

Key Takeaways


Three major advisories from CISA address 17 vulnerabilities across products from LOYTEC Electronics GmbH, Hughes Network Systems, and Baxter.

Multiple products are affected by vulnerabilities allowing for the cleartext transmission of sensitive data, such as passwords, which could be exploited through Man-in-the-Middle (MitM) attacks. Despite being reported in 2021, these vulnerabilities are now publicly disclosed due to the vendor’s lack of response.

With 629 internet-exposed instances, primarily in Italy and France, the likelihood of exploitation is high. Proof of Concepts (PoCs) for these vulnerabilities is publicly available.

Other notable vulnerabilities include insufficiently protected credentials and SQL injection, affecting critical infrastructure systems.

Overview

The Cybersecurity and Infrastructure Security Agency (CISA) has highlighted multiple vulnerabilities in ICS products from LOYTEC Electronics GmbH, Hughes Network Systems, and Baxter. Cyble Research & Intelligence Labs (CRIL) stressed critical vulnerabilities and threats identified between September 03, 2024, and September 09, 2024. These vulnerabilities span a range of severity levels and impact various products from LOYTEC Electronics GmbH, Hughes Network Systems, and Baxter.

Multiple vulnerabilities have been identified in LOYTEC Electronics GmbH’s product line. These issues primarily involve the cleartext transmission and storage of sensitive information, along with missing authentication for critical functions and improper access control. Specifically, CVE-2023-46380, CVE-2023-46382, CVE-2023-46383, and CVE-2023-46385 are high-severity vulnerabilities that expose sensitive data such as passwords to potential interception through Man-in-the-Middle (MitM) attacks. These vulnerabilities affect multiple products, including LINX-151, LINX-212, LVIS-3ME12-A1, and various models within the LIOB and L-INX Configurator series.

For instance, CVE-2023-46380 and CVE-2023-46382 both deal with cleartext transmission of sensitive information. The risk associated with these vulnerabilities is significant because attackers can intercept and read sensitive data sent over the network. Exploiting CVE-2023-46384 and CVE-2023-46386, which involve cleartext storage of sensitive information, further compounds the risk, as attackers gaining access to these stored data could potentially exploit it for unauthorized purposes.

Additionally, CVE-2023-46381 and CVE-2023-46387 address missing authentication and improper access control issues. These vulnerabilities allow unauthorized access to critical functions and systems, which can lead to broader system compromises if exploited. The absence of proper authentication mechanisms in these cases means that attackers could bypass security measures and gain unauthorized control.

Hughes Network Systems Vulnerabilities

Hughes Network Systems’ WL3000 Fusion Software is affected by two medium-severity vulnerabilities. CVE-2024-39278 and CVE-2024-42495 highlight insufficiently protected credentials and missing encryption of sensitive data, respectively. CVE-2024-39278 exposes credentials that are not adequately protected, which could be intercepted and misused by attackers.

On the other hand, CVE-2024-42495 involves missing encryption for sensitive data, increasing the risk of data breaches and unauthorized access. These vulnerabilities affect versions of the software before 2.7.0.10, emphasizing the importance of updating to the latest versions to mitigate these risks.

Baxter Vulnerabilities

Baxter’s Connex Health Portal has been identified with critical and high-severity vulnerabilities. CVE-2024-6795 is a critical SQL injection vulnerability that affects all versions of the Connex Health Portal, released before August 30, 2024. SQL injection vulnerabilities allow attackers to execute arbitrary SQL commands on the database, potentially leading to unauthorized data access or modification.

In addition, CVE-2024-6796 involves improper access control, which can result in unauthorized access to sensitive application areas. Both vulnerabilities necessitate immediate patching and updates to protect against potential exploits.

The vulnerabilities identified across these ICS products highlight critical risks that need prompt attention. For LOYTEC Electronics GmbH products, the issues primarily involve data security flaws, while Hughes Network Systems and Baxter face vulnerabilities that affect credential protection and data encryption.

Organizations using these systems should prioritize applying available patches and updates, implementing robust access controls, and enhancing their security posture to mitigate the risks posed by these vulnerabilities. The majority of disclosed vulnerabilities are categorized as high severity, emphasizing the critical need for prompt action and mitigation.

Conclusion

These vulnerabilities highlight critical security issues in ICS products from LOYTEC Electronics GmbH, Hughes Network Systems, and Baxter. Key vulnerabilities include cleartext transmission of sensitive data, SQL injection, and improper access controls, all of which pose significant risks. Organizations must act quickly by applying patches, enhancing access controls, and improving security monitoring. These steps are crucial to mitigating the identified risks and protecting critical infrastructure from exploitation.

Mitigations and Recommendations


Implement network segmentation to isolate ICS networks from corporate and internet networks. Use firewalls and DMZs to manage traffic between segments.

Apply strong, multifactor authentication and limit access based on the principle of least privilege.

Keep ICS hardware and software updated with the latest patches to defend against known vulnerabilities.

Deploy monitoring tools to detect suspicious activities and maintain logs for forensic investigations.

Develop and test an ICS-specific incident response plan for effective handling of security incidents.

Educate staff on ICS-specific threats and best practices, emphasizing the risks of social engineering and untrusted software sources.

Sources


https://www.cisa.gov/news-events/ics-advisories/icsa-24-247-01

https://www.cisa.gov/news-events/ics-advisories/icsa-24-249-01

https://www.cisa.gov/news-events/ics-medical-advisories/icsma-24-249-01

The post Major ICS Security Flaws Disclosed in LOYTEC, Hughes, and Baxter Products appeared first on Cyble.

Blog – Cyble – ​Read More