CVE-2024-1198: CWE-502 Deserialization in openBI
A vulnerability, which was classified as critical, was found in openBI up to 6.0.3. Affected is the function addxinzhi of the file application/controllers/User.php of the component Phar Handler. The manipulation of the argument outimgurl leads to deserialization. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-252696.
AI Analysis
Technical Summary
CVE-2024-1198 is a critical deserialization vulnerability (CWE-502) identified in the openBI software versions up to 6.0.3. The vulnerability exists in the addxinzhi function within the User.php controller file, specifically in the Phar Handler component. The flaw arises from improper handling of the 'outimgurl' argument, which is subject to deserialization without adequate validation or sanitization. This allows an attacker to remotely manipulate serialized data, potentially injecting malicious payloads during the deserialization process. Such exploitation can lead to arbitrary code execution, data tampering, or denial of service. The vulnerability is remotely exploitable without requiring user interaction but does require some level of privileges (as indicated by the CVSS vector's PR:L). The CVSS 3.1 base score is 6.3, categorized as medium severity, reflecting the balance between the ease of exploitation and the impact on confidentiality, integrity, and availability. Although no public exploits are currently known in the wild, the disclosure of the exploit details increases the risk of active exploitation. The vulnerability affects all openBI versions from 6.0.0 through 6.0.3, which are used for business intelligence and data visualization purposes, often deployed in enterprise environments for data analytics and reporting.
Potential Impact
For European organizations, this vulnerability poses a significant risk, especially for those relying on openBI for critical business intelligence operations. Successful exploitation could lead to unauthorized access to sensitive business data, manipulation of analytics results, or disruption of reporting services, impacting decision-making processes. The compromise of data integrity and availability could affect compliance with European data protection regulations such as GDPR, potentially resulting in legal and financial penalties. Additionally, the ability to execute arbitrary code remotely could allow attackers to pivot within the network, escalating privileges or deploying ransomware. Organizations in sectors like finance, manufacturing, and public administration, which heavily depend on BI tools, may face operational disruptions and reputational damage. The medium CVSS score suggests a moderate but non-negligible threat level, warranting prompt attention to prevent exploitation.
Mitigation Recommendations
To mitigate this vulnerability, European organizations should immediately identify and inventory all instances of openBI versions 6.0.0 through 6.0.3 within their environments. Since no official patches are currently linked, organizations should consider the following specific actions: 1) Implement strict input validation and sanitization on the 'outimgurl' parameter to prevent malicious serialized data from being processed. 2) Restrict access to the vulnerable addxinzhi function by applying network segmentation and access control lists to limit exposure to trusted users and systems only. 3) Employ runtime application self-protection (RASP) or web application firewalls (WAF) with custom rules to detect and block suspicious deserialization payloads targeting the Phar Handler. 4) Monitor logs and network traffic for unusual activity related to deserialization attempts or unexpected behavior in openBI services. 5) Engage with the openBI community or vendors for updates or patches and plan for timely upgrades once available. 6) Conduct security awareness training for developers and administrators on secure deserialization practices to prevent similar vulnerabilities in custom code.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Spain, Poland, Sweden
CVE-2024-1198: CWE-502 Deserialization in openBI
Description
A vulnerability, which was classified as critical, was found in openBI up to 6.0.3. Affected is the function addxinzhi of the file application/controllers/User.php of the component Phar Handler. The manipulation of the argument outimgurl leads to deserialization. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-252696.
AI-Powered Analysis
Technical Analysis
CVE-2024-1198 is a critical deserialization vulnerability (CWE-502) identified in the openBI software versions up to 6.0.3. The vulnerability exists in the addxinzhi function within the User.php controller file, specifically in the Phar Handler component. The flaw arises from improper handling of the 'outimgurl' argument, which is subject to deserialization without adequate validation or sanitization. This allows an attacker to remotely manipulate serialized data, potentially injecting malicious payloads during the deserialization process. Such exploitation can lead to arbitrary code execution, data tampering, or denial of service. The vulnerability is remotely exploitable without requiring user interaction but does require some level of privileges (as indicated by the CVSS vector's PR:L). The CVSS 3.1 base score is 6.3, categorized as medium severity, reflecting the balance between the ease of exploitation and the impact on confidentiality, integrity, and availability. Although no public exploits are currently known in the wild, the disclosure of the exploit details increases the risk of active exploitation. The vulnerability affects all openBI versions from 6.0.0 through 6.0.3, which are used for business intelligence and data visualization purposes, often deployed in enterprise environments for data analytics and reporting.
Potential Impact
For European organizations, this vulnerability poses a significant risk, especially for those relying on openBI for critical business intelligence operations. Successful exploitation could lead to unauthorized access to sensitive business data, manipulation of analytics results, or disruption of reporting services, impacting decision-making processes. The compromise of data integrity and availability could affect compliance with European data protection regulations such as GDPR, potentially resulting in legal and financial penalties. Additionally, the ability to execute arbitrary code remotely could allow attackers to pivot within the network, escalating privileges or deploying ransomware. Organizations in sectors like finance, manufacturing, and public administration, which heavily depend on BI tools, may face operational disruptions and reputational damage. The medium CVSS score suggests a moderate but non-negligible threat level, warranting prompt attention to prevent exploitation.
Mitigation Recommendations
To mitigate this vulnerability, European organizations should immediately identify and inventory all instances of openBI versions 6.0.0 through 6.0.3 within their environments. Since no official patches are currently linked, organizations should consider the following specific actions: 1) Implement strict input validation and sanitization on the 'outimgurl' parameter to prevent malicious serialized data from being processed. 2) Restrict access to the vulnerable addxinzhi function by applying network segmentation and access control lists to limit exposure to trusted users and systems only. 3) Employ runtime application self-protection (RASP) or web application firewalls (WAF) with custom rules to detect and block suspicious deserialization payloads targeting the Phar Handler. 4) Monitor logs and network traffic for unusual activity related to deserialization attempts or unexpected behavior in openBI services. 5) Engage with the openBI community or vendors for updates or patches and plan for timely upgrades once available. 6) Conduct security awareness training for developers and administrators on secure deserialization practices to prevent similar vulnerabilities in custom code.
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-02-02T07:57:08.832Z
- Cisa Enriched
- true
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 682d9819c4522896dcbd8d74
Added to database: 5/21/2025, 9:08:41 AM
Last enriched: 7/5/2025, 9:39:58 AM
Last updated: 10/16/2025, 5:35:01 AM
Views: 26
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-0275: CWE-306 Missing Authentication for Critical Function in HCL Software BigFix Mobile
MediumCVE-2025-0274: CWE-306 Missing Authentication for Critical Function in HCL Software BigFix Modern Client Management
MediumCVE-2025-11814: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in Brainstorm Force Ultimate Addons for WPBakery
MediumCVE-2025-62580: CWE-121 Stack-based Buffer Overflow in Delta Electronics ASDA-Soft
HighCVE-2025-62579: CWE-121 Stack-based Buffer Overflow in Delta Electronics ASDA-Soft
HighActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.