Recent bundles
February Security Advisory Ivanti Connect Secure (ICS),Ivanti Policy Secure (IPS) and Ivanti Secure Access Client (ISAC) (Multiple CVEs)
Primary Product
Connect-Secure
Created Date
Feb 11, 2025 3:01:15 PM
Last Modified Date
Feb 11, 2025 3:37:50 PM
Summary
Ivanti has released updates for Ivanti Connect Secure (ICS),Ivanti Policy Secure (IPS) and Ivanti Secure Access Client (ISAC) which addresses medium, high and critical severity vulnerabilities.
We are not aware of any customers being exploited by these vulnerabilities at the time of disclosure.
Vulnerability Details
CVE Number
Description
CVSS Score (Severity)
CVSS Vector
CWE
Impacted Products
CVE-2024-38657
External control of a file name in Ivanti Connect Secure before version 22.7R2.4 and Ivanti Policy Secure before version 22.7R1.3 allows a remote authenticated attacker with admin privileges to write arbitrary files.
9.1 (Critical)
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
CWE-73
Connect Secure & Policy Secure
CVE-2025-22467
A stack-based buffer overflow in Ivanti Connect Secure before version 22.7R2.6 allows a remote authenticated attacker to achieve remote code execution.
9.9 (Critical)
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CWE-121
Connect Secure
CVE-2024-10644
Code injection in Ivanti Connect Secure before version 22.7R2.4 and Ivanti Policy Secure before version 22.7R1.3 allows a remote authenticated attacker with admin privileges to achieve remote code execution.
9.1 (Critical)
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
CWE-94
Connect Secure & Policy Secure
CVE-2024-12058
External control of a file name in Ivanti Connect Secure before version 22.7R2.6 and Ivanti Policy Secure before version 22.7R1.3 allows a remote authenticated attacker with admin privileges to read arbitrary files.
6.8 (Medium)
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N
CWE-73
Connect Secure & Policy Secure
CVE-2024-13830
Reflected XSS in Ivanti Connect Secure before version 22.7R2.6 and Ivanti Policy Secure before version 22.7R1.3 allows a remote unauthenticated attacker to obtain admin privileges. User interaction is required.
6.1 (Medium)
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
CWE-79
Connect Secure & Policy Secure
CVE-2024-13842
A hardcoded key in Ivanti Connect Secure before version 22.7R2.3 and Ivanti Policy Secure before version 22.7R1.3 allows a local unauthenticated attacker to read sensitive data.
6.0 (Medium)
CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N
CWE-321
Connect Secure & Policy Secure
CVE-2024-13843
Cleartext storage of information in Ivanti Connect Secure before version 22.7R2.6 and Ivanti Policy Secure before version 22.7R1.3 allows a local unauthenticated attacker to read sensitive data.
6.0 (Medium)
CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N
CWE-312
Connect Secure & Policy Secure
CVE-2024-13813
Insufficient permissions in Ivanti Secure Access Client before version 22.8R1 allows a local authenticated attacker to delete arbitrary files.
7.1 (High)
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
CWE-732
Secure Access Client
Affected Versions
Product Name
Affected Versions
Resolved Versions
Patch Availability
Ivanti Connect Secure (ICS)
22.7R2.5 and below
22.7R2.6
Download Portal
Ivanti Policy Secure (IPS)
22.7R1.2 and below
22.7R1.3
Download Portal
Ivanti Secure Access Client (ISAC)
22.7R4 and below
22.8R1
Download Portal
Solution
These vulnerabilities are resolved on the latest version of the product and can be accessed in the download portal (Login Required):
- Ivanti Connect Secure 22.7R2.6
- Ivanti Policy Secure 22.7R1.3
- Ivanti Secure Access Client 22.8R1
Acknowledgements
Ivanti would like to thank the following for reporting the relevant issues and for working with Ivanti to help protect our customers:
- Matthew Galligan, CISA Rapid Action Force (CVE-2024-38657)
- Ori David of Akamai (CVE-2024-37374, CVE-2024-37375)
- sim0nsecurity of HackerOne (CVE-2024-13813)
Note: Ivanti is dedicated to ensuring the security and integrity of our enterprise software products. We recognize the vital role that security researchers, ethical hackers, and the broader security community play in identifying and reporting vulnerabilities. Visit HERE to learn more about our Vulnerability Disclosure Policy.
FAQ
- Are you aware of any active exploitation of these vulnerabilities?
We are not aware of any customers being exploited by these vulnerabilities prior to public disclosure. These vulnerabilities were disclosed through our responsible disclosure program.
- How can I tell if I have been compromised?
Currently, there is no known public exploitation of this vulnerability that could be used to provide a list of indicators of compromise. - What should I do if I need help?
If you have questions after reviewing this information, you can log a case and/or request a call via the Success Portal
- Are any of these vulnerability fixes backported to any of the 9.x versions?
No. The Pulse Connect Secure 9.x version of the product reached End of Engineering June 2024 and has reached End-of-Support as of December 31, 2024. Because of this, the 9.x version of Connect Secure no longer receives backported fixes. We strongly encourage customers to upgrade to Ivanti Connect Secure 22.7 to benefit from important security updates that we have made throughout the solution.
- What does it mean when a vulnerability describes remote authenticated attackers?
It means that an attacker who is able to interact with the vulnerable component and pass authentication is able to exploit the vulnerability.
Article Number :
000097586
Related vulnerabilities: CVE-2024-12058CVE-2024-10644CVE-2024-13830CVE-2024-13843CVE-2024-38657CVE-2024-13813CVE-2024-37374CVE-2024-13842CVE-2025-22467CVE-2024-37375
Unauthenticated RCE on Some Netgear WiFi Routers, PSV-2023-0039
2025-02-10T18:09:14 by Cédric BonhommeNETGEAR has released fixes for an unauthenticated RCE security vulnerability on the following product models:
- XR1000 fixed in firmware version 1.0.0.74
- XR1000v2 fixed in firmware version 1.1.0.22
- XR500 fixed in firmware version 2.3.2.134
NETGEAR strongly recommends that you download the latest firmware as soon as possible.
Related vulnerabilities: PSV-2023-0039CVE-2025-25246
Summary
Zyxel recently became aware of CVE-2024-40890 and CVE-2024-40891 being mentioned in a post on GreyNoise’s blog. Additionally, VulnCheck informed us that they will publish the technical details regarding CVE-2024-40891 and CVE-2025-0890 on their blog. We have confirmed that the affected models reported by VulnCheck, VMG1312-B10A, VMG1312-B10B, VMG1312-B10E, VMG3312-B10A, VMG3313-B10A, VMG3926-B10B, VMG4325-B10A, VMG4380-B10A, VMG8324-B10A, VMG8924-B10A, SBG3300, and SBG3500, are legacy products that have reached end-of-life (EOL) for years. Therefore, we strongly recommend that users replace them with newer-generation products for optimal protection. What are the vulnerabilities?
CVE-2024-40890
UNSUPPORTED WHEN ASSIGNED
A post-authentication command injection vulnerability in the CGI program of certain legacy DSL CPE models, including VMG1312-B10A, VMG1312-B10B, VMG1312-B10E, VMG3312-B10A, VMG3313-B10A, VMG3926-B10B, VMG4325-B10A, VMG4380-B10A, VMG8324-B10A, VMG8924-B10A, SBG3300, and SBG3500, could allow an authenticated attacker to execute operating system (OS) commands on an affected device by sending a crafted HTTP POST request. It is important to note that WAN access is disabled by default on these devices, and this attack can only be successful if user-configured passwords have been compromised.
CVE-2024-40891
UNSUPPORTED WHEN ASSIGNED
A post-authentication command injection vulnerability in the management commands of certain legacy DSL CPE models, including VMG1312-B10A, VMG1312-B10B, VMG1312-B10E, VMG3312-B10A, VMG3313-B10A, VMG3926-B10B, VMG4325-B10A, VMG4380-B10A, VMG8324-B10A, VMG8924-B10A, SBG3300, and SBG3500. This vulnerability could allow an authenticated attacker to execute OS commands on an affected device via Telnet. It is important to note that WAN access and the Telnet function are disabled by default on these devices, and this attack can only be successful if the user-configured passwords have been compromised.
CVE-2025-0890
UNSUPPORTED WHEN ASSIGNED
Insecure default credentials for the Telnet function in certain legacy DSL CPE models, including VMG1312-B10A, VMG1312-B10B, VMG1312-B10E, VMG3312-B10A, VMG3313-B10A, VMG3926-B10B, VMG4325-B10A, VMG4380-B10A, VMG8324-B10A, VMG8924-B10A, SBG3300, and SBG3500, could allow an attacker to log in to the management interface if the administrators have the option to change the default credentials but fail to do so. It is important to note that WAN access and the Telnet function are disabled by default on these devices. What should you do?
The following models—VMG1312-B10A, VMG1312-B10B, VMG1312-B10E, VMG3312-B10A, VMG3313-B10A, VMG3926-B10B, VMG4325-B10A, VMG4380-B10A, VMG8324-B10A, VMG8924-B10A, SBG3300, and SBG3500—are legacy products that have reached EOL status for several years. In accordance with industry product life cycle management practices, Zyxel advises customers to replace these legacy products with newer-generation equipment for optimal protection. If you obtained your Zyxel product through an internet service provider (ISP), please contact the ISP for support. For ISPs, please contact your Zyxel sales or service representatives for further details.
Additionally, disabling remote access and periodically changing passwords are proactive measures that can help prevent potential attacks.
Coordinated Timeline:
- 2024-07-13: VulnCheck notified Zyxel about vulnerabilities in the EOL CPE VMG4325-B10A without providing any reports.
- 2024-07-14: Zyxel requested VulnCheck to provide a detailed report; however, VulnCheck did not respond.
- 2024-07-31: VulnCheck published CVE-2024-40890 and CVE-2024-40891 on their blog without informing Zyxel.
- 2025-01-28: GreyNoise published CVE-2024-40890 and CVE-2024-40891 on their blog.
- 2025-01-29: Zyxel received VulnCheck’s report regarding CVE-2024-40890, CVE-2024-40891, and CVE-2025-0890.
- 2025-01-29: Zyxel became aware of the vulnerabilities in certain legacy DSL CPE models.
Related vulnerabilities: CVE-2025-0890CVE-2024-40891CVE-2024-40890
Android Security Bulletin February 2025 Published February 3, 2025
The Android Security Bulletin contains details of security vulnerabilities affecting Android devices. Security patch levels of 2025-02-05 or later address all of these issues. To learn how to check a device's security patch level, see Check and update your Android version.
Android partners are notified of all issues at least a month before publication. Source code patches for these issues have been released to the Android Open Source Project (AOSP) repository and linked from this bulletin. This bulletin also includes links to patches outside of AOSP.
The most severe of these issues is a high security vulnerability in the Framework component that could lead to local escalation of privilege with no additional execution privileges needed. The severity assessment is based on the effect that exploiting the vulnerability would possibly have on an affected device, assuming the platform and service mitigations are turned off for development purposes or if successfully bypassed.
Refer to the Android and Google Play Protect mitigations section for details on the Android security platform protections and Google Play Protect, which improve the security of the Android platform. Android and Google service mitigations
This is a summary of the mitigations provided by the Android security platform and service protections such as Google Play Protect. These capabilities reduce the likelihood that security vulnerabilities could be successfully exploited on Android.
Exploitation for many issues on Android is made more difficult by enhancements in newer versions of the Android platform. We encourage all users to update to the latest version of Android where possible.
The Android security team actively monitors for abuse through Google Play Protect and warns users about Potentially Harmful Applications. Google Play Protect is enabled by default on devices with Google Mobile Services, and is especially important for users who install apps from outside of Google Play.
Note: There are indications that CVE-2024-53104 may be under limited, targeted exploitation. 2025-02-01 security patch level vulnerability details
In the sections below, we provide details for each of the security vulnerabilities that apply to the 2025-02-01 patch level. Vulnerabilities are grouped under the component they affect. Issues are described in the tables below and include CVE ID, associated references, type of vulnerability, severity, and updated AOSP versions (where applicable). When available, we link the public change that addressed the issue to the bug ID, like the AOSP change list. When multiple changes relate to a single bug, additional references are linked to numbers following the bug ID. Devices with Android 10 and later may receive security updates as well as Google Play system updates. Framework
The most severe vulnerability in this section could lead to local escalation of privilege with no additional execution privileges needed. CVE References Type Severity Updated AOSP versions CVE-2024-49721 A-354682735 EoP High 12, 12L, 13 CVE-2024-49743 A-305695605 [2] [3] EoP High 12, 12L, 13, 14, 15 CVE-2024-49746 A-359179312 [2] EoP High 12, 12L, 13, 14, 15 CVE-2025-0097 A-364037868 EoP High 15 CVE-2025-0098 A-367266072 EoP High 15 CVE-2025-0099 A-370962373 EoP High 15 CVE-2023-40122 A-286235483 ID High 12, 12L, 13, 14, 15 CVE-2023-40133 A-283264674 ID High 12, 12L, 13 CVE-2023-40134 A-283101289 ID High 12, 12L, 13 CVE-2023-40135 A-281848557 ID High 12, 12L, 13 CVE-2023-40136 A-281666022 ID High 12, 12L, 13 CVE-2023-40137 A-281665050 ID High 12, 12L, 13 CVE-2023-40138 A-281534749 ID High 12, 12L, 13 CVE-2023-40139 A-281533566 ID High 12, 12L, 13 CVE-2024-0037 A-292104015 ID High 12, 12L, 13, 14, 15 CVE-2025-0100 A-372670004 ID High 12, 12L, 13, 14, 15 CVE-2024-49741 A-353240784 DoS High 12, 12L, 13, 14, 15 Platform
The vulnerability in this section could lead to local escalation of privilege with no additional execution privileges needed. CVE References Type Severity Updated AOSP versions CVE-2025-0094 A-352542820 EoP High 12, 12L, 13, 14, 15 System
The most severe vulnerability in this section could lead to local escalation of privilege with no additional execution privileges needed. CVE References Type Severity Updated AOSP versions CVE-2025-0091 A-366401629 EoP High 12, 12L, 13, 14, 15 CVE-2025-0095 A-356117796 EoP High 14, 15 CVE-2025-0096 A-356630194 EoP High 15 CVE-2024-49723 A-357870429 [2] ID High 15 CVE-2024-49729 A-368069390 ID High 12, 12L, 13, 14, 15 Google Play system updates
The following issues are included in Project Mainline components. Subcomponent CVE Conscrypt CVE-2024-49723 2025-02-05 security patch level vulnerability details
In the sections below, we provide details for each of the security vulnerabilities that apply to the 2025-02-05 patch level. Vulnerabilities are grouped under the component they affect. Issues are described in the tables below and include CVE ID, associated references, type of vulnerability, severity, and updated AOSP versions (where applicable). When available, we link the public change that addressed the issue to the bug ID, like the AOSP change list. When multiple changes relate to a single bug, additional references are linked to numbers following the bug ID. Kernel
The most severe vulnerability in this section could lead to physical escalation of privilege with no additional execution privileges needed. CVE References Type Severity Subcomponent CVE-2024-53104 A-378455392 Upstream kernel [2] EoP High UVC CVE-2025-0088 A-377672115 Upstream kernel [2] EoP High mremap Arm components
This vulnerability affects Arm components and further details are available directly from Arm. The severity assessment of this issue is provided directly by Arm. CVE References Severity Subcomponent CVE-2025-0015 A-376311652 * High Mali Imagination Technologies
These vulnerabilities affect Imagination Technologies components and further details are available directly from Imagination Technologies. The severity assessment of these issues is provided directly by Imagination Technologies. CVE References Severity Subcomponent CVE-2024-43705 A-372931317 PP-160756 High PowerVR-GPU CVE-2024-46973 A-379728401 PP-160739 High PowerVR-GPU CVE-2024-47892 A-365954523 PP-160576 * High PowerVR-GPU CVE-2024-52935 A-380478495 PP-171230* High PowerVR-GPU MediaTek components
These vulnerabilities affect MediaTek components and further details are available directly from MediaTek. The severity assessment of these issues is provided directly by MediaTek. CVE References Severity Subcomponent CVE-2025-20634 A-381773169 M-MOLY01289384 * High Modem CVE-2024-20141 A-381773173 M-ALPS09291402 * High DA CVE-2024-20142 A-381773175 M-ALPS09291406 * High DA CVE-2025-20635 A-381771695 M-ALPS09403752 * High DA CVE-2025-20636 A-381773171 M-ALPS09403554 * High secmem Unisoc components
This vulnerability affects Unisoc components and further details are available directly from Unisoc. The severity assessment of this issue is provided directly by Unisoc. CVE References Severity Subcomponent CVE-2024-39441 A-381429835 U-2811333 * High Android Qualcomm components
These vulnerabilities affect Qualcomm components and are described in further detail in the appropriate Qualcomm security bulletin or security alert. The severity assessment of these issues is provided directly by Qualcomm. CVE References Severity Subcomponent CVE-2024-45569 A-377311993 QC-CR#3852339 Critical WLAN CVE-2024-45571 A-377313069 QC-CR#3834424 High WLAN CVE-2024-45582 A-377312377 QC-CR#3868093 High Camera CVE-2024-49832 A-377312238 QC-CR#3874301 High Camera CVE-2024-49833 A-377312639 QC-CR#3874372 [2] [3] [4] High Camera CVE-2024-49834 A-377312055 QC-CR#3875406 High Camera CVE-2024-49839 A-377311997 QC-CR#3895196 High WLAN CVE-2024-49843 A-377313194 QC-CR#3883522 High Display Qualcomm closed-source components
These vulnerabilities affect Qualcomm closed-source components and are described in further detail in the appropriate Qualcomm security bulletin or security alert. The severity assessment of these issues is provided directly by Qualcomm. CVE References Severity Subcomponent CVE-2024-38404 A-357616389 * High Closed-source component CVE-2024-38420 A-357616296 * High Closed-source component Common questions and answers
This section answers common questions that may occur after reading this bulletin.
- How do I determine if my device is updated to address these issues?
To learn how to check a device's security patch level, see Check and update your Android version.
Security patch levels of 2025-02-01 or later address all issues associated with the 2025-02-01 security patch level.
Security patch levels of 2025-02-05 or later address all issues associated with the 2025-02-05 security patch level and all previous patch levels.
Device manufacturers that include these updates should set the patch string level to:
[ro.build.version.security_patch]:[2025-02-01]
[ro.build.version.security_patch]:[2025-02-05]
For some devices on Android 10 or later, the Google Play system update will have a date string that matches the 2025-02-01 security patch level. Please see this article for more details on how to install security updates.
- Why does this bulletin have two security patch levels?
This bulletin has two security patch levels so that Android partners have the flexibility to fix a subset of vulnerabilities that are similar across all Android devices more quickly. Android partners are encouraged to fix all issues in this bulletin and use the latest security patch level.
Devices that use the 2025-02-01 security patch level must include all issues associated with that security patch level, as well as fixes for all issues reported in previous security bulletins.
Devices that use the security patch level of 2025-02-05 or newer must include all applicable patches in this (and previous) security bulletins.
Partners are encouraged to bundle the fixes for all issues they are addressing in a single update.
- What do the entries in the Type column mean?
Entries in the Type column of the vulnerability details table reference the classification of the security vulnerability. Abbreviation Definition RCE Remote code execution EoP Elevation of privilege ID Information disclosure DoS Denial of service N/A Classification not available
- What do the entries in the References column mean?
Entries under the References column of the vulnerability details table may contain a prefix identifying the organization to which the reference value belongs. Prefix Reference A- Android bug ID QC- Qualcomm reference number M- MediaTek reference number N- NVIDIA reference number B- Broadcom reference number U- UNISOC reference number
- What does an * next to the Android bug ID in the References column mean?
Issues that are not publicly available have an * next to the corresponding reference ID. The update for that issue is generally contained in the latest binary drivers for Pixel devices available from the Google Developer site.
- Why are security vulnerabilities split between this bulletin and device / partner security bulletins, such as the Pixel bulletin?
Security vulnerabilities that are documented in this security bulletin are required to declare the latest security patch level on Android devices. Additional security vulnerabilities that are documented in the device / partner security bulletins are not required for declaring a security patch level. Android device and chipset manufacturers may also publish security vulnerability details specific to their products, such as Google, Huawei, LGE, Motorola, Nokia, or Samsung.
Related vulnerabilities: CVE-2024-49723CVE-2024-52935CVE-2024-49729CVE-2025-20634CVE-2025-0099CVE-2024-49834CVE-2025-0095CVE-2024-49832CVE-2023-40134CVE-2024-49833CVE-2025-0098CVE-2025-0100CVE-2024-49839CVE-2024-49743CVE-2025-0015CVE-2023-40138CVE-2025-0097CVE-2024-45571CVE-2023-40139CVE-2025-20635CVE-2025-0091CVE-2023-40137CVE-2024-49741CVE-2024-53104CVE-2024-49721CVE-2024-38404CVE-2024-45569CVE-2025-20636CVE-2025-0088CVE-2024-45582CVE-2024-38420CVE-2025-0096CVE-2024-20142CVE-2023-40135CVE-2024-0037CVE-2024-46973CVE-2024-47892CVE-2024-49843CVE-2023-40122CVE-2023-40133CVE-2024-49746CVE-2023-40136CVE-2024-39441CVE-2024-43705CVE-2024-20141CVE-2025-0094
Threat Actors Use CVE-2019-18935 to Deliver Reverse Shells and…
2025-02-03T13:12:08 by Alexandre DulaunoyThreat Actors Use CVE-2019-18935 to Deliver Reverse Shells and…
BY eSentire Threat Response Unit (TRU)
Adversaries don’t work 9-5 and neither do we. At eSentire, our 24/7 SOCs are staffed with Elite Threat Hunters and Cyber Analysts who hunt, investigate, contain and respond to threats within minutes.
We have discovered some of the most dangerous threats and nation state attacks in our space – including the Kaseya MSP breach and the more_eggs malware.
Our Security Operations Centers are supported with Threat Intelligence, Tactical Threat Response and Advanced Threat Analytics driven by our Threat Response Unit – the TRU team.
In TRU Positives, eSentire’s Threat Response Unit (TRU) provides a summary of a recent threat investigation. We outline how we responded to the confirmed threat and what recommendations we have going forward.
Here’s the latest from our TRU Team… What did we find?
In early January 2025, the eSentire Threat Response Unit (TRU) identified an unknown threat actor(s) exploiting the now six year old vulnerability, CVE-2019-18935, in Progress Telerik UI for ASP.NET AJAX.
TRU observed threat actor(s) using the w3wp.exe (IIS worker process) to load a reverse shell and run follow up commands for reconnaissance through cmd.exe. Reverse shells were dropped in the C:\Windows\Temp directory matching [10 digits].[6 digits].dll and [10 digits].[7 digits].dll.
The infection process begins when the threat actor(s) send a specific request to the IIS server to determine if the file upload handler is available. This can be seen in IIS logs as shown below:
2025-01-03 10:25:51 10.22.12.20 GET /Telerik.Web.UI.WebResource.axd type=rau 443 - - - 200 0 0 171
After confirming the file upload handler is available and determining the software version is vulnerable, the threat actor(s) made use of a customized version of the PoC here to upload and execute a remote shell.
The reverse shell is simple and is a mixed mode .NET assembly containing a routine that serves to connect to the C2 at 213.136.75[.]130 via Windows Sockets. The legitimate windows binary cmd.exe is started and the input/output/error handles are redirected to threat actor control. Figure 1 – Decompiled reverse shell Figure 1 – Decompiled reverse shell
After the threat actor(s) established connection via the reverse shell, they executed several commands to get information about users on the system. The figure below contains the parent/child relationships and subsequent commands executed through the reverse shell to enumerate users via net.exe and net1.exe. Figure 2 – Remote shell loaded by w3wp.exe IIS worker process leading to recon commands Figure 2 – Remote shell loaded by w3wp.exe IIS worker process leading to recon commands
The following Yara rule can be used for detecting the reverse shell. This Yara rule is also available for download here.
rule TCP_Reverse_Shell_Windows_x64 { meta: description = "Detects Windows based 64-bit TCP reverse shell" author = "YungBinary" hash = "b971bf43886e3ab1d823477826383dfaee1e2935788226a285c7aebeabee7348" strings: $winsock_2_0 = { 66 B? 02 00 FF 15 } $winsock_2_1 = { 66 B? 02 01 FF 15 } $winsock_2_2 = { 66 B? 02 02 FF 15 } $winsock_1_0 = { 66 B? 01 00 FF 15 } $winsock_1_1 = { 66 B? 01 01 FF 15 }
$socket_params = {
41 B8 06 00 00 00
BA 01 00 00 00
B9 02 00 00 00
}
$cmd = {
48 C7 44 24 ?? 00 00 00 00
48 C7 44 24 ?? 00 00 00 00
C7 44 24 ?? 00 00 00 00
C7 44 24 ?? (01 | 00) 00 00 00
45 33 C9
45 33 C0
48 8D 15 ?? ?? ?? ??
33 C9
FF 15
}
$wait = {
BA FF FF FF FF
48 8B 4C ?? ??
FF 15
}
condition:
uint16(0) == 0x5a4d and ((1 of ($winsock*)) and $socket_params and $cmd and $wait)
}
Figure 3 – Yara rule to detect Windows TCP reverse shell
TRU also observed the threat actor(s) dropping the open-source privilege escalation tool JuicyPotatoNG on the host under various file names:
C:\Users\Public\PingCaler.exe
C:\Users\Public\JuicyPotatoNG.exe
The following batch files were also dropped on the host but the purpose of these files is not known at this time:
C:\Users\Public\rdp.bat
C:\Users\Public\user.bat
C:\Users\Public\All.bat
The following diagram provided by Telerik can be used to determine if your specific version of Telerik UI for ASP.NET AJAX is vulnerable. Figure 4 – Vulnerable version decision tree diagram, source Figure 4 – Vulnerable version decision tree diagram, source. What did we do?
Our team of 24/7 SOC Cyber Analysts proactively isolated the affected host to contain the infection on the customer’s behalf.
We communicated what happened with the customer and helped them with incident remediation efforts.
What can you learn from this TRU Positive?
While the vulnerability in Progress Telerik UI for ASP.NET AJAX is several years old, it continues to be a viable entry point for threat actors.
This highlights the importance of patching systems, especially if they are going to be exposed to the internet.
Recommendations from the Threat Response Unit (TRU):
Implement a comprehensive vulnerability management service with robust patch management solution and process to ensure systems are up to date with the latest security patches before exposing them to the Internet.
Use an Endpoint Detection and Response (EDR) solution and ensure it is deployed across all workstations and servers.
Indicators of Compromise
You can access the Indicators of Compromise here. References
https://www.esentire.com/security-advisories/active-exploitation-of-cve-2019-18935
https://bishopfox.com/blog/cve-2019-18935-remote-code-execution-in-telerik-ui
https://www.telerik.com/products/aspnet-ajax/documentation/knowledge-base/common-allows-javascriptserializer-deserialization
https://github.com/noperator/CVE-2019-18935
https://www.cisa.gov/news-events/cybersecurity-advisories/aa23-074a
https://github.com/antonioCoco/JuicyPotatoNG
Related vulnerabilities: CVE-2019-18935
CISA released a fact sheet, Contec CMS8000 Contains a Backdoor, detailing an analysis of three firmware package versions of the Contec CMS8000, a patient monitor used by the U.S. Healthcare and Public Health (HPH) sector. Analysts discovered that an embedded backdoor function with a hard-coded IP address, CWE – 912: Hidden Functionality (CVE-2025-0626), and functionality that enables patient data spillage, CWE – 359: Exposure of Private Personal Information to an Unauthorized Actor (CVE-2025-0683
), exists in all versions analyzed.
Please note the Contec CMS8000 may be re-labeled and sold by resellers. For a list of known re-labeled devices, please refer to FDA’s safety communication, Cybersecurity Vulnerabilities with Certain Patient Monitors from Contec and Epsimed: FDA Safety Communication.
Contec Medical Systems, the company which manufactures this monitor as well as other medical device and healthcare solutions, is headquartered in Qinhuangdao, China. The Contec CMS8000 is used in medical settings across the U.S. and European Union to provide continuous monitoring of a patient’s vital signs—tracking electrocardiogram, heart rate, blood oxygen saturation, non-invasive blood pressure, temperature, and respiration rate. CISA assesses that inclusion of this backdoor in the firmware of the patient monitor can create conditions which may allow remote code execution and device modification with the ability to alter its configuration. This introduces risk to patient safety as a malfunctioning patient monitor could lead to an improper response to patient vital signs.
CISA strongly urges HPH sector organizations review the fact sheet and implement FDA's mitigations. Visit CISA’s Healthcare and Public Health Cybersecurity page to learn more about how to help improve cybersecurity within the HPH sector. For more information and guidance on protection against the most common and impactful threats, tactics, techniques, and procedures, visit CISA’s Cross-Sector Cybersecurity Performance Goals.
Related vulnerabilities: CVE-2025-0683CVE-2025-0626
CISA, in partnership with the Federal Bureau of Investigation (FBI), released Threat Actors Chained Vulnerabilities in Ivanti Cloud Service Applications. This advisory was crafted in response to active exploitation of vulnerabilities—CVE-2024-8963, an administrative bypass vulnerability; CVE-2024-9379, a SQL injection vulnerability; and CVE-2024-8190 and CVE-2024-9380, remote code execution vulnerabilities—in Ivanti Cloud Service Appliances (CSA) in September 2024.
CISA, and the use of trusted third-party incident response data, found that threat actors chained the listed vulnerabilities to gain initial access, conduct remote code execution (RCE), obtain credentials, and implant webshells on victim networks.
CISA and FBI strongly encourage network administrators and defenders to upgrade to the latest supported version of Ivanti CSA and to hunt for malicious activity on their networks using the detection methods and indicators of compromise (IOCs) provided in the advisory. All members of the cybersecurity community are also encouraged to visit CISA’s Known Exploited Vulnerabilities Catalog to help better manage vulnerabilities and keep pace with threat activity. For more information and guidance on protection against the most common and impactful threats, tactics, techniques, and procedures, visit CISA’s Cross-Sector Cybersecurity Performance Goals.
Related vulnerabilities: CVE-2024-8963CVE-2024-9379CVE-2024-9380CVE-2024-8190
Vulnerabilities in CMSimple 5.16 leading to RCE
- CVE-2024-57546 - An issue in CMSimple v.5.16 allows a remote attacker to obtain sensitive information via a crafted script to the validate link function.
- CVE-2024-57547 - Insecure Permissions vulnerability in CMSimple v.5.16 allows a remote attacker to obtain sensitive information via a crafted script to the Functionality of downloading php backup files.
- CVE-2024-57548 - CMSimple 5.16 allows the user to edit log.php file via print page.
- CVE-2024-57549 - CMSimple 5.16 allows the user to read cms source code through manipulation of the file name in the file parameter of a GET request.
Original research
https://github.com/h4ckr4v3n/cmsimple5.16_research
Related vulnerabilities: CVE-2024-57546CVE-2024-57547CVE-2024-57549CVE-2024-57548
A triple-exploit chain. auth bypass (1) to exposed dbus interface (2) to command injection (3): https://www.exploit-db.com/exploits/45100
Related vulnerabilities: CVE-2018-10660CVE-2018-10662CVE-2018-10661
On Jan. 8, 2025, Ivanti released a security advisory for two vulnerabilities (CVE-2025-0282 and CVE-2025-0283) in its Connect Secure, Policy Secure and ZTA gateway products. This threat brief provides attack details that we observed in a recent incident response engagement to provide actionable intelligence to the community. These details can be used to further detect current attacks noted in the wild using CVE-2025-0282.
These Ivanti products are all appliances that facilitate remote connections into a network. As such, they are outward-facing assets that attackers could target to infiltrate a network.
CVE-2025-0282 is a stack-based buffer overflow in Ivanti Connect Secure before version 22.7R2.5, Ivanti Policy Secure before version 22.7R1.2 and Ivanti Neurons for ZTA gateways before version 22.7R2.3 that allows a remote unauthenticated attacker to achieve remote code execution. This vulnerability has been assigned a critical CVSS score of 9.0.
CVE-2025-0283 is a stack-based buffer overflow in Ivanti Connect Secure before version 22.7R2.5, Ivanti Policy Secure before version 22.7R1.2 and Ivanti Neurons for ZTA gateways before version 22.7R2.3 that allows a local authenticated attacker to escalate their privileges. This vulnerability has been assigned a high CVSS score of 7.0.
On the same day of Ivanti’s advisory, Mandiant disclosed its findings of attacks in the wild using the CVE-2025-0282 remote code execution vulnerability.
On January 10, Watchtowr Labs also provided analysis of the exploited vulnerability. On January 12, Watchtowr provided a walkthrough and on January 16 they published a proof of concept (PoC).
For more info https://unit42.paloaltonetworks.com/threat-brief-ivanti-cve-2025-0282-cve-2025-0283/
Related vulnerabilities: CVE-2025-0283CVE-2025-0282