Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-4428: CWE-94: Improper Control of Generation of Code ('Code Injection') in Ivanti Endpoint Manager Mobile

0
High
VulnerabilityCVE-2025-4428cvecve-2025-4428cwe-94
Published: Tue May 13 2025 (05/13/2025, 15:46:55 UTC)
Source: CVE
Vendor/Project: Ivanti
Product: Endpoint Manager Mobile

Description

Remote Code Execution in API component in Ivanti Endpoint Manager Mobile 12.5.0.0 and prior on unspecified platforms allows authenticated attackers to execute arbitrary code via crafted API requests.

AI-Powered Analysis

AILast updated: 10/21/2025, 21:21:14 UTC

Technical Analysis

CVE-2025-4428 is a remote code execution (RCE) vulnerability identified in the API component of Ivanti Endpoint Manager Mobile, specifically in version 12.5.0.0 and earlier. The root cause is improper control over the generation of code, classified under CWE-94, which typically involves unsafe dynamic code execution or injection of code through user-controllable inputs. In this case, authenticated attackers with elevated privileges can craft malicious API requests that cause the system to execute arbitrary code. This vulnerability affects unspecified platforms supported by the product, indicating a broad potential impact across different operating systems. The attack vector is network-based (AV:N), requires low attack complexity (AC:L), but does require privileges (PR:H) and no user interaction (UI:N). The scope is unchanged (S:U), meaning the impact is confined to the vulnerable component. The vulnerability impacts confidentiality, integrity, and availability (C:H/I:H/A:H), allowing attackers to fully compromise the affected system. Although no public exploits are known at this time, the vulnerability is critical for organizations using Ivanti Endpoint Manager Mobile to manage mobile endpoints, as it could lead to full system compromise, data breaches, or disruption of mobile device management services. The lack of available patches at the time of disclosure necessitates immediate mitigation through access restrictions and monitoring. Ivanti Endpoint Manager Mobile is widely used in enterprise environments for mobile device management, making this vulnerability a significant concern for IT security teams.

Potential Impact

For European organizations, this vulnerability poses a substantial risk to the security of mobile device management infrastructure. Successful exploitation could lead to unauthorized code execution, enabling attackers to compromise sensitive data, disrupt endpoint management operations, or pivot to other internal systems. This could result in data breaches, loss of control over mobile endpoints, and potential regulatory non-compliance under GDPR due to compromised personal or corporate data. The high severity and ease of exploitation with authenticated access mean that insider threats or compromised credentials could be leveraged to exploit this flaw. Organizations relying on Ivanti Endpoint Manager Mobile for critical infrastructure, finance, healthcare, or government sectors in Europe could face operational disruptions and reputational damage. The absence of known exploits currently provides a window for proactive defense, but the threat landscape could rapidly evolve once exploit code becomes available.

Mitigation Recommendations

1. Immediately restrict access to the Ivanti Endpoint Manager Mobile API to trusted administrators and networks using network segmentation and firewall rules. 2. Enforce the principle of least privilege by reviewing and limiting user accounts with elevated privileges capable of accessing the API. 3. Implement strong multi-factor authentication (MFA) for all users with API access to reduce the risk of credential compromise. 4. Monitor API access logs for unusual or suspicious activity indicative of exploitation attempts. 5. Coordinate with Ivanti for timely updates and patches; apply security patches as soon as they become available. 6. Conduct internal audits and penetration tests focusing on API security to identify and remediate other potential weaknesses. 7. Educate administrators on the risks of code injection vulnerabilities and safe API usage practices. 8. Consider deploying web application firewalls (WAFs) or API gateways with rules to detect and block malicious payloads targeting code injection vectors. 9. Prepare incident response plans specifically addressing potential exploitation of this vulnerability to enable rapid containment and recovery.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
ivanti
Date Reserved
2025-05-08T07:50:52.767Z
Cisa Enriched
true
Cvss Version
3.1
State
PUBLISHED

Threat ID: 682cd0f81484d88663aeb2f2

Added to database: 5/20/2025, 6:59:04 PM

Last enriched: 10/21/2025, 9:21:14 PM

Last updated: 11/22/2025, 7:25:14 PM

Views: 32

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats