CVE-2024-0986: CWE-78 OS Command Injection in Issabel PBX
A vulnerability was found in Issabel PBX 4.0.0. It has been rated as critical. This issue affects some unknown processing of the file /index.php?menu=asterisk_cli of the component Asterisk-Cli. The manipulation of the argument Command leads to os command injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-252251. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.
AI Analysis
Technical Summary
CVE-2024-0986 is a security vulnerability identified in Issabel PBX version 4.0.0, specifically within the Asterisk-Cli component accessed via the /index.php?menu=asterisk_cli endpoint. The vulnerability is classified as an OS command injection (CWE-78), where improper sanitization or validation of the 'Command' argument allows an attacker to inject arbitrary operating system commands. This flaw can be exploited remotely without user interaction, but requires high privileges (PR:H) on the system to initiate the attack. Although the CVSS 3.1 base score is rated at 4.7 (medium severity), the potential impact includes unauthorized command execution that could compromise system confidentiality, integrity, and availability. The vulnerability was publicly disclosed on January 28, 2024, and no official patch or vendor response has been provided to date. The lack of vendor engagement increases the risk for organizations relying on this PBX solution, as attackers could develop exploits to leverage this weakness. The vulnerability affects only version 4.0.0 of Issabel PBX, a popular open-source unified communications platform integrating Asterisk for telephony services. Given the critical nature of PBX systems in managing voice communications, exploitation could lead to disruption of telephony services, data leakage, or pivoting into internal networks.
Potential Impact
For European organizations, the exploitation of this vulnerability could have significant operational and security consequences. PBX systems like Issabel are often integral to enterprise telephony infrastructure, handling internal and external voice communications. Successful exploitation could allow attackers to execute arbitrary commands on the PBX server, potentially leading to interception or manipulation of calls, disruption of communication services, or use of the compromised system as a foothold for lateral movement within the corporate network. This could impact sectors relying heavily on telephony, such as finance, healthcare, government, and critical infrastructure. Additionally, compromised PBX systems might be leveraged for toll fraud or launching further attacks. The absence of a vendor patch and public exploit code increases the urgency for European organizations to assess their exposure and implement mitigations promptly. The medium CVSS score reflects the requirement for high privileges, which somewhat limits exploitation scope, but insider threats or compromised credentials could facilitate attack execution.
Mitigation Recommendations
Given the lack of an official patch, European organizations should implement several targeted mitigations: 1) Restrict access to the /index.php?menu=asterisk_cli endpoint by enforcing strict network segmentation and firewall rules, allowing only trusted administrative IP addresses to connect. 2) Employ strong authentication and credential management to prevent unauthorized access with high privileges required for exploitation. 3) Monitor PBX logs and network traffic for unusual command execution patterns or access attempts to the vulnerable endpoint. 4) Consider deploying web application firewalls (WAFs) with custom rules to detect and block command injection payloads targeting the 'Command' parameter. 5) If feasible, isolate the PBX system from other critical infrastructure to limit lateral movement. 6) Evaluate alternative PBX solutions or earlier versions without this vulnerability until a vendor patch is released. 7) Maintain up-to-date backups of PBX configurations and data to enable rapid recovery in case of compromise. 8) Engage in threat intelligence sharing within industry groups to stay informed about emerging exploits related to this vulnerability.
Affected Countries
Germany, France, United Kingdom, Italy, Spain, Netherlands, Poland, Belgium
CVE-2024-0986: CWE-78 OS Command Injection in Issabel PBX
Description
A vulnerability was found in Issabel PBX 4.0.0. It has been rated as critical. This issue affects some unknown processing of the file /index.php?menu=asterisk_cli of the component Asterisk-Cli. The manipulation of the argument Command leads to os command injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-252251. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.
AI-Powered Analysis
Technical Analysis
CVE-2024-0986 is a security vulnerability identified in Issabel PBX version 4.0.0, specifically within the Asterisk-Cli component accessed via the /index.php?menu=asterisk_cli endpoint. The vulnerability is classified as an OS command injection (CWE-78), where improper sanitization or validation of the 'Command' argument allows an attacker to inject arbitrary operating system commands. This flaw can be exploited remotely without user interaction, but requires high privileges (PR:H) on the system to initiate the attack. Although the CVSS 3.1 base score is rated at 4.7 (medium severity), the potential impact includes unauthorized command execution that could compromise system confidentiality, integrity, and availability. The vulnerability was publicly disclosed on January 28, 2024, and no official patch or vendor response has been provided to date. The lack of vendor engagement increases the risk for organizations relying on this PBX solution, as attackers could develop exploits to leverage this weakness. The vulnerability affects only version 4.0.0 of Issabel PBX, a popular open-source unified communications platform integrating Asterisk for telephony services. Given the critical nature of PBX systems in managing voice communications, exploitation could lead to disruption of telephony services, data leakage, or pivoting into internal networks.
Potential Impact
For European organizations, the exploitation of this vulnerability could have significant operational and security consequences. PBX systems like Issabel are often integral to enterprise telephony infrastructure, handling internal and external voice communications. Successful exploitation could allow attackers to execute arbitrary commands on the PBX server, potentially leading to interception or manipulation of calls, disruption of communication services, or use of the compromised system as a foothold for lateral movement within the corporate network. This could impact sectors relying heavily on telephony, such as finance, healthcare, government, and critical infrastructure. Additionally, compromised PBX systems might be leveraged for toll fraud or launching further attacks. The absence of a vendor patch and public exploit code increases the urgency for European organizations to assess their exposure and implement mitigations promptly. The medium CVSS score reflects the requirement for high privileges, which somewhat limits exploitation scope, but insider threats or compromised credentials could facilitate attack execution.
Mitigation Recommendations
Given the lack of an official patch, European organizations should implement several targeted mitigations: 1) Restrict access to the /index.php?menu=asterisk_cli endpoint by enforcing strict network segmentation and firewall rules, allowing only trusted administrative IP addresses to connect. 2) Employ strong authentication and credential management to prevent unauthorized access with high privileges required for exploitation. 3) Monitor PBX logs and network traffic for unusual command execution patterns or access attempts to the vulnerable endpoint. 4) Consider deploying web application firewalls (WAFs) with custom rules to detect and block command injection payloads targeting the 'Command' parameter. 5) If feasible, isolate the PBX system from other critical infrastructure to limit lateral movement. 6) Evaluate alternative PBX solutions or earlier versions without this vulnerability until a vendor patch is released. 7) Maintain up-to-date backups of PBX configurations and data to enable rapid recovery in case of compromise. 8) Engage in threat intelligence sharing within industry groups to stay informed about emerging exploits related to this vulnerability.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- VulDB
- Date Reserved
- 2024-01-28T15:21:08.336Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 68387d4f182aa0cae28316e6
Added to database: 5/29/2025, 3:29:19 PM
Last enriched: 7/7/2025, 11:42:45 PM
Last updated: 8/10/2025, 1:46:50 PM
Views: 17
Related Threats
CVE-2025-5048: CWE-120 Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') in Autodesk AutoCAD
HighCVE-2025-5047: CWE-457: Use of Uninitialized Variable in Autodesk AutoCAD
HighCVE-2025-5046: CWE-125 Out-of-Bounds Read in Autodesk AutoCAD
HighCVE-2025-54466: CWE-94 Improper Control of Generation of Code ('Code Injection') in Apache Software Foundation Apache OFBiz
CriticalCVE-2025-9053: SQL Injection in projectworlds Travel Management System
MediumActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.