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

Vulnerability in Acrobat Reader could lead to remote code execution; Microsoft patches information disclosure issue in Windows API

Cisco Talos’ Vulnerability Research team discovered two vulnerabilities have been disclosed and fixed over the past few weeks. 

Talos discovered a time-of-check time-of-use vulnerability in Adobe Acrobat Reader, one of the most popular PDF readers currently available, and an information disclosure vulnerability in the Microsoft Windows AllJoyn API. 

For Snort coverage that can detect the exploitation of these vulnerabilities, download the latest rule sets from Snort.org, and our latest Vulnerability Advisories are always posted on Talos Intelligence’s website

Microsoft AllJoyn API information disclosure vulnerability 

 
The AllJoyn API in some versions of the Microsoft Windows operating system contains an information disclosure vulnerability. 

TALOS-2024-1980 (CVE-2024-38257) could allow an adversary to view uninitialized memory on the targeted machine. 

AllJoyn is a DCOM-like framework for creating method calls or sending one-way signals between applications on a distributed bus. It primarily is used in internet-of-things (IoT) devices to tell the devices to perform certain tasks, like turning lights on or off or reading the temperature of a space. 

Microsoft fixed this issue as part of its monthly security update on Tuesday. For more on Patch Tuesday, read Talos’ blog here

CVE-2024-38257 is considered “less likely” to be exploited, though it does not require any user interaction or user privileges.   

Adobe Acrobat Reader annotation object page race condition  

Discovered by KPC. 

Adobe Acrobat Reader, one of the most popular pieces of PDF reading software currently available, contains a time-of-check, use-after-free vulnerability that could trigger memory corruption, and eventually, arbitrary code execution. 

TALOS-2024-2011 (CVE-2024-39420) can be executed if an adversary tricks a targeted user into opening a specially crafted PDF file with malicious JavaScript embedded. This JavaScript could then trigger memory corruption due to a race condition.  

Depending on the memory layout of the process this vulnerability affects, it may be possible to abuse this vulnerability for arbitrary read and write access, which could ultimately be abused to achieve arbitrary code execution. 

Cisco Talos Blog – ​Read More

How to Analyze Malware in ANY.RUN Sandbox: Eric Parker’s Guide

Recently, Eric Parker, a cybersecurity expert and YouTuber, released a new video on ANY.RUN’s interactive sandbox. We recommend you take a look at his tutorial, as it offers a step-by-step guide on how to use the service and save time on reverse engineering.

Here’s our overview of the key highlights from the video. 

About malware analysis in a sandbox 

Sandboxing is a crucial process in cybersecurity that lets professionals analyze malware in a controlled environment. Sandboxes provide a safe space to upload and examine potentially malicious samples without compromising your actual system.

ANY.RUN’s sandbox offers interactive analysis, providing users with a real-time view of how malware behaves and allowing them to engage with the system and samples just like on a standard computer.

Try advanced malware analysis with ANY.RUN for free 



Get 14-day trial


Setting up a sandbox environment 

Eric began by highlighting various settings of ANY.RUN that can be adjusted for different scenarios, including: 

MITM Proxy: This setting is particularly useful for intercepting and analyzing network traffic, such as HTTP requests made by the malware. This allows you to track how the malware communicates with command and control (C2) servers and gather more detailed information about its actions. 

Network settings in ANY.RUN sandbox 

FakeNet: This option is effective if you’re worried about malware with worm-like capabilities, allowing detection of network shares or interactions with non-functional command and control servers. 

Learn more about MITM proxy and FakeNet 

Operating system customization in ANY.RUN sandbox 

Operating System Customization: ANY.RUN offers a variety of OS options, from older versions of Windows (7/32-bit, 7/64-bit) to the latest Windows 11. Linux users can also run samples for cross-platform analysis.  

For legacy malware, using an older OS might be necessary for full compatibility. Eric recommends experimenting with different OS options based on the malware sample. 

Pre-installed soft set: You can choose pre-installed software sets, such as Office or Complete, to simulate real-world environments, making the analysis more realistic. Users can also upload their own tools to the virtual machine for quick access during the investigation. 

Privacy Settings: You can choose whether your analysis results are public or private. If you’re working with sensitive malware samples that could contain proprietary information, this feature ensures confidentiality. 

Duration Control: For malware that delays execution (e.g., with sleep functions), you can extend the sandbox runtime to capture the full scope of its behavior. 

Sandbox analysis of Zombie malware 

In the video demonstration, Eric uploaded a malware sample he suspected of being malware. ANY.RUN’s sandbox quickly identified warning signs, detecting file replacements and abnormal behaviors indicative of malware infection. 

Key points in the analysis: 

File overwriting: The malware replaced files with an executable payload. In the example, the malicious EXE was found to overwrite legitimate system files and create numerous temporary files. 

File dumping: One of ANY.RUN’s most valuable features was the ability to dump files mid-execution, making it easier to analyze malware that uses packing or encryption to conceal its malicious actions. 

File dumping in ANY.RUN sandbox

Executable identification: Uploading the file to the sandbox made it possible to instantly identify it as malicious and belonging to the Zombie malware family. 

Analysis of Pysilon Discord RAT 

Eric emphasized that the goal of any malware analyst is not to understand every line of code, but to get a good view of how the program interacts with the system. This is where an interactive sandbox can prove extremely helpful.  

By running the malware in a virtual environment, analysts can quickly understand its behavior without delving into advanced reverse engineering.

In many cases, dynamic analysis alone can provide all the necessary information, bypassing the need for a full static analysis. Eric showed this by running a Pysilon Discord RAT sample in the sandbox.

Try all features of ANY.RUN sandbox for free 



Get 14-day trial


Pysilon is a malware that is often packed in a unique way, making static analysis more difficult. To avoid dealing with the packer, Eric simply enabled the MITM proxy in ANY.RUN, which allowed him to acquire the malware’s Discord bot token in a few seconds. 

Bot token acquired in ANY.RUN sandbox 

ANY.RUN also identified a newly spawned executable named “driveinst.exe” which mimicked a legitimate process. This executable was flagged as unsigned, raising a red flag. 

ANY.RUN automatically categorized the malware as a stealer, highlighting its malicious actions and network communications. 

Pysilon Discord RAT analysis inside ANY.RUN sandbox 

As a result, the bot token was captured, the malware’s behavior was observed, and the analysis was completed in less than 30 seconds.

Conclusion 

Sandboxes, as demonstrated by Eric Parker, are a powerful tool in the fight against malware. Sandbox analysis allowed Eric to extract crucial information within minutes, cutting down the time needed for manual reverse engineering.

The sandbox provided live data on network traffic, file manipulation, and system changes, delivering instant feedback on malware behavior.

Eric was able to avoid the need to manually unpack or decrypt files, streamlining the analysis process.

To see full potential of ANY.RUN’s sandbox, request a 14-day free trial →

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 LookupYARA Search and Feeds, help you find IOCs or files to learn more about the threats and respond to incidents faster.

The post How to Analyze Malware in ANY.RUN Sandbox: Eric Parker’s Guide appeared first on ANY.RUN’s Cybersecurity Blog.

ANY.RUN’s Cybersecurity Blog – ​Read More

Four zero-days included in group of 79 vulnerabilities Microsoft discloses, including one with 9.8 severity score

Microsoft disclosed four vulnerabilities that are actively being exploited in the wild as part of its regular Patch Tuesday security update this week in what’s become a regular occurrence for the company’s patches in 2024. 

Two of the zero-day vulnerabilities, CVE-2024-38226 and CVE-2024-38014, exist in the Microsoft Publisher software and Windows Installer, respectively. Last month, Microsoft disclosed six vulnerabilities in its Patch Tuesday that were already being exploited in the wild.  

In all, September’s monthly round of patches from Microsoft included 79 vulnerabilities, seven of which are considered critical. In addition to the zero-days disclosed Tuesday, Microsoft also fixed a security issue that had already been publicly disclosed: CVE-2024-38217, a vulnerability in Windows Mark of the Web that could allow an adversary to bypass usual MOTW detection techniques.  

Cisco Talos’ Vulnerability Research team also discovered an information disclosure vulnerability in the AllJoyn API that could allow an adversary to access uninitialized memory. CVE-2024-38257 is considered “less likely” to be exploited, though it does not require any user interaction or user privileges.  

The most serious of the issues included in September’s Patch Tuesday is CVE-2024-43491, which has a severity score of 9.8 out of 10. CVE-2024-43491, a remote code execution issue in Windows Update, is considered “more likely” to be exploited, though Microsoft disclosed few details about the nature of this vulnerability. 

There are also four remote code execution vulnerabilities in SharePoint Server that are also considered “more likely” to be exploited: CVE-2024-38018, CVE-2024-38227, CVE-2024-38228 and CVE-2024-43464

In the case of the latter three vulnerabilities, an authenticated attacker with Site Owner permissions can inject arbitrary code and execute code in the context of SharePoint Server. However, an attacker only needs to have Site Member permissions to exploit CVE-2024-38018. 

CVE-2024-38226, one of the zero-days disclosed this week, is a security feature bypass vulnerability in Microsoft Publisher that could allow an attacker to bypass the default Microsoft Office macro policies used to block untrusted or malicious files. An adversary could exploit this vulnerability by tricking a user into opening a specially crafted, malicious file in Microsoft Publisher, which could lead to a local attack on the victim’s machine. Macros have been blocked by default on Office software to prevent attackers from hiding malicious code in them.  

Another vulnerability being actively exploited in the wild, CVE-2024-38014, is an issue in Windows Installer that could allow an adversary to gain SYTEM-level privileges. This issue affects Windows 11, version 24H2, which is currently only available on certain Microsoft Copilot+ devices, among other older versions of Windows 10 and 11. 

A complete list of all the other vulnerabilities Microsoft disclosed this month is available on its update page

In response to these vulnerability disclosures, Talos is releasing a new Snort rule set that detects attempts to exploit some of them. Please note that additional rules may be released at a future date and current rules are subject to change pending additional information. Cisco Security Firewall customers should use the latest update to their ruleset by updating their SRU. Open-source Snort Subscriber Rule Set customers can stay up to date by downloading the latest rule pack available for purchase on Snort.org

The rules included in this release that protect against the exploitation of many of these vulnerabilities are 63979 – 63984 and 63987 – 63994. There are also Snort 3 rules 301008 – 301013.

Cisco Talos Blog – ​Read More

CISA Adds Three Critical Vulnerabilities to Known Exploited Vulnerabilities Catalog

Key Takeaways


CISA has updated its Known Exploited Vulnerabilities (KEV) Catalog with three critical vulnerabilities: CVE-2016-3714, CVE-2017-1000253, and CVE-2024-40766.

These vulnerabilities are being actively exploited by cybercriminals, posing significant risks to both federal and private sector organizations.

CISA urges all organizations to prioritize the remediation of these vulnerabilities to strengthen their cybersecurity defenses.

Organizations should update software with the latest patches, implement multi-factor authentication (MFA), and continuously monitor for unusual activities.

For detailed information and support, organizations should consult CISA’s advisories and the relevant vendor resources.

Overview

The Cybersecurity and Infrastructure Security Agency (CISA) has recently updated its Known Exploited Vulnerabilities (KEV) Catalog by adding three new vulnerabilities. These newly identified flaws represent significant security risks and are actively being exploited by malicious actors.

The newly added vulnerabilities include CVE-2016-3714, which affects ImageMagick due to improper input validation; CVE-2017-1000253, a Linux kernel vulnerability involving stack buffer corruption in position-independent executables (PIE); and CVE-2024-40766, a severe access control issue in SonicWall SonicOS.

These vulnerabilities are known to be frequent targets for cyberattacks and present significant risks to both federal and private sector organizations. CISA urges all organizations to prioritize remediation of these vulnerabilities to enhance their cybersecurity posture.

Details of the Vulnerabilities

CVE-2016-3714, also known as “ImageTragick,” affects ImageMagick versions prior to 6.9.3-10 and 7.x before 7.0.1-1. This vulnerability arises from improper input validation, which impacts various coders within ImageMagick.

Exploiting this flaw allows attackers to execute arbitrary code via shell metacharacters in a specially crafted image, potentially leading to remote code execution. To mitigate this risk, users should ensure that image files are validated for correct “magic bytes” and configure ImageMagick’s policy file to disable the vulnerable coders. Comprehensive guidance on configuration and additional mitigations is available for users.

CVE-2017-1000253 affects multiple versions of the Linux kernel, including those used in RedHat Enterprise Linux and CentOS. This vulnerability involves stack buffer corruption in the load_elf_binary() function, which can be exploited by local attackers to escalate privileges through issues with position-independent executables (PIE). Users are advised to apply the available patches to correct this buffer corruption flaw. Further details and patches are provided for addressing this issue.

CVE-2024-40766 is a critical vulnerability affecting SonicWall Firewalls Gen 5, Gen 6, and Gen 7 devices running SonicOS 7.0.1-5035 and older. This flaw in SonicWall SonicOS Management Access and SSLVPN allows unauthenticated attackers to gain unauthorized access to the management interface, which could result in unauthorized resource access or even firewall crashes.

To mitigate this vulnerability, it is essential to restrict firewall management to trusted sources or disable WAN management and SSLVPN access from the Internet. Users should download and apply the latest patches from SonicWall’s official site, and detailed security measures and patch links are available for further guidance.

Conclusion

The addition of CVE-2016-3714, CVE-2017-1000253, and CVE-2024-40766 to CISA’s KEV Catalog highlights the critical nature of these vulnerabilities. Organizations must act promptly to address these issues by applying patches and implementing recommended security practices. For additional information and support, refer to the official advisories and technical resources provided by CISA and relevant vendors.

Mitigation and Recommendations


Ensure all software, firmware, and systems are updated with the latest patches.

Restrict access to critical systems to authorized users only and implement multi-factor authentication (MFA).

Continuously monitor systems for unusual activities and conduct regular security audits and vulnerability assessments.

Maintain and regularly update an incident response plan to manage potential security breaches effectively.

Develop a comprehensive strategy for patch management, including inventory, assessment, testing, and deployment.

Implement proper network segmentation to protect critical assets from internet exposure.

The post CISA Adds Three Critical Vulnerabilities to Known Exploited Vulnerabilities Catalog appeared first on Cyble.

Blog – Cyble – ​Read More

The Re-Emergence of CVE-2024-32113: How CVE-2024-45195 has amplified Exploitation Risks

Overview

On September 7, 2024, Cyble Global Sensor Intelligence (CGSI) identified the active exploitation of CVE-2024-32113, a critical path traversal vulnerability in the Apache OFBiz open-source enterprise resource planning (ERP) system. This flaw was initially addressed on April 12, 2024, with a formal patch released on May 8, 2024. CVE-2024-32113 allows Threat Actors (TAs) to execute arbitrary commands by sending specially crafted requests, enabling them to gain unauthorized access and execute arbitrary commands.

On September 4, 2024, the identification of CVE-2024-45195 reignited concerns surrounding Apache OFBiz by revealing a bypass for several previously addressed vulnerabilities, notably CVE-2024-32113. This development has intensified the exploitation of CVE-2024-32113, as attackers exploit the flaw’s resurgence to compromise vulnerable systems and deploy malicious payloads. Researchers also observed active exploitation of this vulnerability to deploy the Mirai botnet on the compromised systems.

Cyble Global Sensor Intelligence (CGSI) findings

Cyble Global Sensor Intelligence (CGSI) detected exploitation attempts of CVE-2024-32113 on September 4, 2024. In the instances recorded by CGSI, as illustrated in the figure below, an attacker attempted to access the endpoint /webtools/control/forgotPassword;/ProgramExport through a POST request.

Vulnerability Details

Remote Code Execution

CVE-2024-32113

CVSSv3.1

9.1

Severity

Critical

Vulnerable Software Versions

Apache OFBi versions before 18.12.13

Description

The affected versions of the Apache OFBiz system contain a Path Traversal vulnerability due to improper limitation of pathnames to restricted directory.

Overview of the Exploit

The vulnerability arises from a fragmented state between the application’s current controller and view map due to the use of different parsing methods for incoming URI patterns. When attackers send unexpected URI requests, the logic for retrieving the authenticated view map can become confused, granting the attacker unauthorized access.

Exploitation occurs when an attacker submits a crafted request to the endpoint /webtools/control/forgotPassword;/ProgramExport, embedding a payload that executes Groovy scripts. This enables arbitrary commands to be run on the server. For instance, a payload could be used to execute the id command, which returns user and group IDs, thereby revealing sensitive information about the server environment.

Mitigation

CVE-2024-32113 affects Apache OFBiz versions prior to 18.12.13. However, version 18.12.13 remains vulnerable to CVE-2024-45195. Therefore, users are advised to upgrade to the latest version, 18.12.16, which addresses both vulnerabilities.

Recommendations

Following are recommendations to defend against the exploitation of CVE-2024-32113 and related vulnerabilities:


Upgrade Apache OFBiz to version 18.12.16 or the latest version available. This version addresses both CVE-2024-32113 and CVE-2024-45195.

Configure and deploy a WAF to filter and monitor HTTP requests, blocking attempts that exploit path traversal and other known attack vectors.

Apply the principle of least privilege to limit the potential impact of any successful exploitation.

Regularly review logs for unusual activities, such as unauthorized access attempts or suspicious requests to vulnerable endpoints.

Indicators of Compromise

Indicators
Indicator
Type

Description

185[.]190[.]24[.]111
IPv4
Malicious IP

References


https://nvd.nist.gov/vuln/detail/CVE-2024-32113

https://nvd.nist.gov/vuln/detail/CVE-2024-45195

https://thehackernews.com/2024/09/apache-ofbiz-update-fixes-high-severity.html

https://www.rapid7.com/blog/post/2024/09/05/cve-2024-45195-apache-ofbiz-unauthenticated-remote-code-execution-fixed/

https://isc.sans.edu/diary/Increased+Activity+Against+Apache+OFBiz+CVE202432113/31132/

https://issues.apache.org/jira/browse/OFBIZ-13006

https://github.com//Mr-xn//CVE-2024-32113

The post The Re-Emergence of CVE-2024-32113: How CVE-2024-45195 has amplified Exploitation Risks appeared first on Cyble.

Blog – Cyble – ​Read More