company logo

Product

Our Product

We are Reshaping the way Developers find and fix vulnerabilities before they get exploited.

Solutions

By Industry

BFSI

Healthcare

Education

IT & Telecom

Government

By Role

CISO/CTO

DevOps Engineer

Resources

Resource Library

Get actionable insight straight from our threat Intel lab to keep you informed about the ever-changing Threat landscape.

Subscribe to Our Weekly Threat Digest

Company

Contact Us

Have queries, feedback or prospects? Get in touch and we shall be with you shortly.

loading..
loading..
loading..
Loading...

Healthcare

Ransomhub

loading..
loading..
loading..

Massive 1.5TB Data Breach Hits Largest US Addiction Treatment, Exposing Patients

BayMark Health Services suffers a massive 1.5TB data breach, exposing patient info from the largest US addiction treatment provider to cybercriminals

10-Jan-2025
4 min read

No content available.

Related Articles

loading..

Zero Day

Learn about CVE-2024-49415, a Samsung phone flaw enabling zero-click attacks via...

Cybersecurity researchers have uncovered a critical vulnerability, CVE-2024-49415, in Samsung smartphones' Monkey’s Audio (APE) decoder. The Monkey’s Audio decoder is a lossless audio compression format designed for high-quality sound reproduction, widely used for efficient storage and playback. Its integration into Samsung smartphones highlights the potential impact on everyday users who rely on seamless media handling. This vulnerability, assigned a CVSS score of 8.1, could enable remote code execution on affected devices running Android 12, 13, and 14. Samsung patched the issue in December 2024 as part of its monthly security updates. The flaw lies in an out-of-bounds write vulnerability within the `libsaped.so` library. An out-of-bounds write occurs when a program writes data outside the boundaries of allocated memory, potentially overwriting adjacent memory and causing unpredictable behavior. This type of vulnerability can be exploited to execute arbitrary code or crash the system. Specifically, it involves improper handling of buffer sizes during audio decoding, creating a potential zero-click exploit if Google Messages is configured with Rich Communication Services (RCS). --- ## Technical Breakdown ### Vulnerability Details - **Library Affected:** `libsaped.so` - **Function:** `saped_rec` - **Buffer Overflow Issue:** The `saped_rec` function writes to a DMA buffer (`dmabuf`) allocated by the C2 media service. This buffer has a fixed size of `0x120000`. However, if the input audio file has: - **Bytes per Sample:** 24 - **Blocks per Frame:** Exceeding allowable limits The function can write up to three times the blocks-per-frame size, leading to a substantial buffer overflow. ### Trigger Conditions 1. **Remote Zero-Click Attack:** - The transcription service decodes audio locally when Google Messages with RCS is enabled. - The attack does not require user interaction, making it a high-risk vector. 2. **Local Reproduction Steps:** - Push a crafted audio file to the device: ``` adb push overflow.ape /sdcard/Music/test.amr ``` - Play the file using Voice Notes through the "My Files" application. 3. **Remote Attack Steps:** - Create an RCS voice message on a test device. - Replace the audio file in the `mediascratchspace` directory with the crafted APE file. - Send the message to the target device. ### Impact Upon triggering, the media codec process crashes. Crash logs indicate: - Signal: SIGSEGV - Faulting library: `libsaped.so` - Overwritten adjacent buffers due to DMA buffer overflow. This is significant because crashing the media codec process can disrupt normal device operations, potentially leading to denial of service (DoS). Additionally, the overflow might be leveraged by attackers to execute arbitrary code, increasing the severity of the exploit. Although direct exploitability is uncertain, the presence of non-DMA data in adjacent buffers raises the likelihood of malicious exploitation. --- ## Related Vulnerabilities In addition to CVE-2024-49415, Samsung’s December 2024 security update addresses: - **CVE-2024-49413** - **Severity:** High (CVSS score: 7.1) - **Component:** SmartSwitch - **Impact:** Enables local attackers to install malicious applications via improper verification of cryptographic signatures. --- ## Mitigation Samsung’s patch for `libsaped.so` introduces proper input validation to prevent buffer overflows. Input validation ensures that incoming data is checked against expected parameters and limits, rejecting malformed or oversized inputs that could otherwise cause vulnerabilities like buffer overflows. Users are advised to: 1. **Update Devices:** Install the December 2024 security update. 2. **Disable RCS Temporarily:** For added security, disable RCS on Google Messages until the patch is applied. ### Verification Researchers and users can verify the patch by checking: - Device Build Version: Ensure the update aligns with SMR Dec-2024 Release 1. - Crash Reproduction: Confirm the crafted APE file no longer causes a crash. --- ## Broader Implications This vulnerability underscores the risks of decoding untrusted media files, particularly in services like Google Messages with automatic decoding features. Similar vulnerabilities in other platforms have demonstrated how attackers exploit automated processes to bypass user interaction. Left unaddressed, these flaws can pave the way for increasingly sophisticated zero-click exploits, emphasizing the need for robust security practices and thorough vetting of media-related functionalities. Key takeaways for device manufacturers include: - **Enhanced Buffer Management:** Implement dynamic buffer allocation where feasible. - **Proactive Security Testing:** Conduct fuzz testing for media codecs to identify edge-case vulnerabilities. For end-users, the incident highlights the importance of timely updates and caution when using services that process untrusted media files automatically. --- ## Conclusion CVE-2024-49415 serves as a reminder of the intricacies involved in modern device security, especially with automated features like RCS-based transcription. While Samsung’s timely patch mitigates the immediate risks, continued vigilance and proactive measures are essential to secure devices against evolving threats. Stay updated with the latest security patches to ensure device integrity and prevent potential exploits. Cybersecurity is a shared responsibility—timely actions from both users and vendors are crucial to mitigating threats effectively.

loading..   10-Jan-2025
loading..   4 min read
loading..

Vulnerability

Network Security

Discover critical Moxa vulnerabilities (CVE-2024-9138 & CVE-2024-9140) impacting...

Taiwan-based Moxa has issued an [advisory](https://www.moxa.com/en/support/product-support/security-advisory/mpsa-241155-privilege-escalation-and-os-command-injection-vulnerabilities-in-cellular-routers,-secure-routers,-and-netwo) regarding two critical security vulnerabilities that impact a range of its network security appliances, including cellular routers and secure routers. These vulnerabilities, if exploited, could lead to privilege escalation and unauthorized command execution, posing significant risks to system integrity and data security, particularly in critical industries such as energy, transportation, and manufacturing. In these sectors, Moxa devices often serve as the backbone of operational technology (OT) networks, where any compromise could disrupt essential services or jeopardize safety systems. ### **Overview of Vulnerabilities** The vulnerabilities, identified as **CVE-2024-9138** and **CVE-2024-9140**, were reported by cybersecurity researcher Lars Haulin. These flaws were uncovered during a targeted security assessment aimed at identifying weaknesses in network appliance firmware, showcasing the importance of proactive audits in preventing potential exploits. They carry high CVSS scores of **8.6** and **9.3**, respectively, underlining their critical nature. #### **CVE-2024-9138** - **Description**: A hard-coded credentials vulnerability that allows authenticated users to escalate privileges. This could grant root-level access to the system. - **Potential Impact**: - Unauthorized modifications to system configurations. - Exposure of sensitive data. - Disruption of essential services. - Full system compromise. #### **CVE-2024-9140** - **Description**: A flaw that allows attackers to bypass input restrictions by exploiting special characters. This could enable unauthorized command execution. - **Potential Impact**: - Execution of malicious commands. - High risk of data theft or system manipulation. ### **Affected Products and Firmware Versions** These vulnerabilities impact multiple Moxa product lines. Below are the affected devices and firmware versions: #### **CVE-2024-9138** - **EDR-810 Series**: Firmware version 5.12.37 and earlier. - **EDR-8010 Series**: Firmware version 3.13.1 and earlier. - **EDR-G902 Series**: Firmware version 5.7.25 and earlier. - **EDR-G9004 Series**: Firmware version 3.13.1 and earlier. - **EDR-G9010 Series**: Firmware version 3.13.1 and earlier. - **EDF-G1002-BP Series**: Firmware version 3.13.1 and earlier. - **NAT-102 Series**: Firmware version 1.0.5 and earlier. - **OnCell G4302-LTE4 Series**: Firmware version 3.13 and earlier. - **TN-4900 Series**: Firmware version 3.13 and earlier. #### **CVE-2024-9140** - **EDR-8010 Series**: Firmware version 3.13.1 and earlier. - **EDR-G9004 Series**: Firmware version 3.13.1 and earlier. - **EDR-G9010 Series**: Firmware version 3.13.1 and earlier. - **EDF-G1002-BP Series**: Firmware version 3.13.1 and earlier. - **NAT-102 Series**: Firmware version 1.0.5 and earlier. - **OnCell G4302-LTE4 Series**: Firmware version 3.13 and earlier. - **TN-4900 Series**: Firmware version 3.13 and earlier. ### **Available Patches and Updates** Moxa has released patches for most of the affected products. Users are advised to take the following actions: #### **Firmware Updates** - **Upgrade to version 3.14 or later** for the following: - EDR-810 Series - EDR-8010 Series - EDR-G902 Series - EDR-G9004 Series - EDR-G9010 Series - EDF-G1002-BP Series - **For Specific Products**: - **NAT-102 Series**: No official patch is currently available. - **OnCell G4302-LTE4 Series**: Contact Moxa Technical Support for updates. - **TN-4900 Series**: Contact Moxa Technical Support for guidance. ### **Mitigation Strategies** For devices where patches are unavailable, or as an additional precaution, Moxa recommends the following measures: 1. **Network Isolation**: Ensure devices are not exposed to the internet directly. 2. **Access Control**: Restrict SSH access to trusted IP addresses and networks using: - Firewall rules. - TCP wrappers. 3. **Monitoring**: Implement intrusion detection and prevention systems to identify and block exploitation attempts. ### **Technical Insights** #### **Understanding the Risks** - Hard-coded credentials, as seen in CVE-2024-9138, are often overlooked during product development. A notable example is the Mirai botnet incident, where attackers exploited hard-coded credentials in IoT devices to build a massive botnet, demonstrating how such vulnerabilities can have widespread and devastating impacts. However, they pose a grave risk, allowing attackers to bypass standard authentication mechanisms and gain elevated privileges. - CVE-2024-9140 demonstrates how inadequate input validation can be exploited to inject malicious commands. Such vulnerabilities are often leveraged in targeted attacks against critical infrastructure. #### **Implications** Moxa’s network appliances are widely used in industrial environments, including energy, transportation, and manufacturing. For instance, in the energy sector, these devices often manage remote monitoring of power grids, ensuring uninterrupted energy supply. In transportation, Moxa’s routers are critical in facilitating communication between traffic management systems, while in manufacturing, they play a vital role in connecting and securing industrial control systems to optimize production processes. Exploiting these vulnerabilities could result in severe operational disruptions, making patching and mitigation efforts crucial.

loading..   07-Jan-2025
loading..   4 min read
loading..

Payload

Backdoor

PLAYFULGHOST malware targets users with keylogging, screen capture, and kernel-l...

In a disturbing new development in the world of security, researchers have identified a sophisticated malware strain dubbed "PLAYFULGHOST" that is capable of a wide range of malicious activities, from keylogging and screen captures to remote shell access and file transfers. The malware has been found to share key functionalities with the notorious Gh0st RAT, a remote administration tool whose source code was leaked in 2008, further fueling concerns about its potential for widespread damage.** Google's Managed Defense team, along with other cybersecurity experts, has revealed that the malware's primary aim is information gathering. It employs a variety of techniques, such as phishing emails, SEO poisoning, and even the hijacking of legitimate VPN applications to silently infect vulnerable systems. Specifically, the attackers have been observed using trojanized versions of popular VPN apps like LetsVPN to gain initial access to target systems. --- ### **Initial Infection Chain: A Multi-Pronged Attack** One of the key vectors for the initial infection involves phishing emails with attachments disguised as image files. In one reported case, a victim was tricked into opening a malicious RAR archive with a ".jpg" extension. Upon extraction, the archive executed a harmful Windows executable that subsequently downloaded and deployed the PLAYFULGHOST payload from a remote server. Another tactic observed in the wild involves SEO poisoning techniques. Cybercriminals manipulate search engine results to direct unsuspecting users to download malware-laced installers masquerading as legitimate software, such as LetsVPN. Once these trojanized installers are launched, they deploy an interim payload responsible for retrieving the backdoor components that enable further exploitation. --- ### **A Stealthy & Persistent Threat** PLAYFULGHOST is designed to evade detection and establish persistence on infected systems through multiple techniques. Among these, attackers use methods like DLL search order hijacking and side-loading to run malicious DLL files that decrypt and execute the malware in memory, making it harder for security solutions to detect. In one particularly sophisticated case, a Windows shortcut file ("QQLaunch.lnk") was observed combining files named "h" and "t" to create a rogue DLL that was then sideloaded through a renamed "curl.exe" file. The malware employs at least four different persistence mechanisms: - Run registry keys - Scheduled tasks - The Windows Startup folder - Windows services These measures ensure that PLAYFULGHOST remains active even after the system is rebooted or attempts are made to disable it. Once embedded, it begins its extensive information-gathering activities, which include recording keystrokes, taking screenshots, capturing audio, stealing system metadata, and even gathering data from QQ accounts and installed security products. Additionally, the malware can erase browser caches, profiles, and local storage for apps like Skype, Telegram, and QQ. It can also block keyboard and mouse input, wipe clipboard data, and perform a variety of file operations. --- ### **Powerful Payloads and Rootkits: Mimikatz and Beyond** The capabilities of PLAYFULGHOST extend beyond mere surveillance. The malware can drop a variety of secondary payloads, including Mimikatz (a tool used to extract credentials from memory), as well as a rootkit designed to hide registry entries, files, and processes associated with the attack. In one instance, the malware was found embedded within a payload called BOOSTWAVE, which acts as a dropper for additional malicious executables. PLAYFULGHOST also leverages a tool known as **Terminator**, an open-source utility that can disable security tools through a technique called **Bring Your Own Vulnerable Driver (BYOVD)**. This method uses signed kernel drivers to bypass security controls and execute malware, making it especially difficult for traditional antivirus software to detect the attack. --- ### **Targeting Chinese-Speaking Users** The malware’s specific targets, including popular Chinese applications like Sogou, QQ, and 360 Safety, suggest that the primary victims of these attacks are Chinese-speaking Windows users. This regional targeting aligns with similar attacks observed in July 2024, where cybersecurity firm eSentire reported a campaign leveraging fake Google Chrome installers to distribute the Gh0st RAT via a dropper called Gh0stGambit. Given the overlap with previous attacks and the use of tools like Terminator, it is clear that the threat actors behind PLAYFULGHOST are highly skilled and capable of bypassing even advanced security mechanisms. These attackers are able to utilize vulnerabilities in hardware drivers to escalate privileges and gain kernel-level access, making it difficult for security teams to mitigate the risk. --- ### **BYOVD: An Old but Dangerous Trick** BYOVD attacks, which exploit flaws in vulnerable drivers to gain kernel-level access, have been a known tactic for years. The **Lazarus Group**, a North Korean advanced persistent threat (APT), was one of the first to make use of such techniques in 2021. More recently, ransomware groups like Cuba and D0nut have leveraged BYOVD exploits to disable security tools and escalate privileges. Although modern endpoint detection and response (EDR) solutions are designed to identify and neutralize vulnerable drivers, the exploitation of such weaknesses remains a significant challenge. According to CrowdStrike, the **Terminator tool** used by PLAYFULGHOST operators was priced as low as $300 USD on Russian cybercrime forums, allowing attackers with limited resources to launch highly effective and stealthy attacks. --- ### **Microsoft's Defense Mechanisms: A Critical Tool for Protection** In light of the growing threat posed by BYOVD attacks, Microsoft has taken proactive steps to secure vulnerable drivers and mitigate the risk of kernel-level exploits. Since 2022, Microsoft has provided a **vulnerable driver blocklist**, which can be activated through Windows Security. This list is updated regularly and can be enforced through Windows Defender Application Control (WDAC). Security teams are strongly encouraged to enable **Hypervisor-enforced Code Integrity (HVCI)** or **S Mode** to block vulnerable drivers. This, along with regular updates to the driver blocklist, provides an effective defense against exploitation attempts that bypass traditional security solutions. --- ### **Stay Ahead of Evolving Threats** The discovery of PLAYFULGHOST highlights the increasingly sophisticated nature of modern cyberattacks. With its combination of advanced infection techniques, persistence mechanisms, and powerful surveillance capabilities, this malware represents a serious threat to both individual users and organizations. To mitigate risks, cybersecurity professionals must ensure they are using the latest security technologies, including EDR/XDR solutions, while also taking proactive steps to block vulnerable drivers. Microsoft’s **Vulnerable Driver Blocklist** provides a valuable tool in this effort, enabling security teams to safeguard their environments against kernel-level exploits that are otherwise difficult to detect. As cybercriminals continue to evolve their tactics, it is essential for organizations to stay informed about emerging threats and to implement comprehensive defense strategies that can adapt to the changing landscape. By leveraging the right tools and best practices, businesses can reduce their exposure to threats like PLAYFULGHOST and other sophisticated malware campaigns.

loading..   04-Jan-2025
loading..   6 min read