VulnerabilityPublished 27 Oct 2024Updated 30 Oct 2024

CVE-2024-50616: Ironman PowerShell Universal 5.x before 5.0.12 allows an authenticated attacker to elevate their

Source CVE Database V5

Not known to be exploited · CVSS 8.8 High · fixed in 5.0.12 : patch affected systems soon.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

8.8High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 5.0.12

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2024-50616, organizations should: 1) Immediately upgrade Ironman PowerShell Universal to version 5.0.12 or later once the patch is available from the vendor. 2) Until patching is possible, restrict access to the PowerShell Universal management interface to only trusted administrators and networks using network segmentation and firewall rules. 3) Enforce the principle of least privilege by reviewing and minimizing user permissions within the PowerShell Universal environment to reduce the risk of privilege escalation. 4) Implement strong authentication mechanisms such as multi-factor authentication (MFA) for all users accessing the platform. 5) Monitor logs and audit trails for unusual activities, especially signs of privilege escalation or unauthorized job information access. 6) Conduct regular security assessments and penetration testing focused on automation platforms to identify and remediate similar vulnerabilities proactively. 7) Educate administrators and users about the risks of privilege escalation and the importance of secure credential management. 8) Maintain an incident response plan that includes procedures for handling automation platform compromises.

Description

Ironman PowerShell Universal 5.x before 5.0.12 allows an authenticated attacker to elevate their privileges and view job information.

Impact

The impact of CVE-2024-50616 is significant for organizations using Ironman PowerShell Universal, as it enables attackers with authenticated access to escalate privileges and access sensitive job information. This can lead to unauthorized disclosure of confidential data, manipulation or disruption of automated workflows, and potentially full system compromise. The high impact on confidentiality, integrity, and availability means attackers could exfiltrate sensitive operational data, alter or sabotage automation tasks, and cause service outages or disruptions. Given the role of PowerShell Universal in managing critical automation and orchestration tasks, exploitation could facilitate lateral movement within networks, enabling attackers to pivot to more sensitive systems or data stores. Organizations relying heavily on PowerShell automation for IT operations, DevOps, or security orchestration are particularly vulnerable. The vulnerability's remote exploitability and low attack complexity increase the likelihood of exploitation once a patch or exploit becomes publicly available. This threat could affect a wide range of sectors including finance, healthcare, government, and technology, where automation platforms are integral to operational efficiency and security.

References

docs.powershelluniversal.com/changelogs/cves (opens in a new tab)

Community reviews

Loading reviews…