CVE-2024-22083VulnerabilityPublished 20 Mar 2024Updated 18 Nov 2024

CVE-2024-22083: n/a

Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

6.5Medium

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

EPSS: 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

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

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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Mar 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 2026-10-26.

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 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

1. Immediately audit network exposure of Elspec G5 devices and restrict access to trusted management networks only, using network segmentation and firewalls. 2. Implement strict access control policies and monitor network traffic for unusual access attempts to these devices. 3. Disable any remote management interfaces if not required or restrict them to secure VPN connections. 4. Contact Elspec or authorized vendors for updates or patches addressing this vulnerability and apply them as soon as they become available. 5. Employ intrusion detection systems (IDS) tuned to detect anomalous activity related to the backdoor session ID usage. 6. Regularly review device configurations and logs for unauthorized changes or access attempts. 7. Consider deploying compensating controls such as multi-factor authentication on management interfaces if supported. 8. Develop and test incident response plans specific to industrial control system compromises involving these devices. 9. Engage with industry information sharing groups to stay informed about emerging threats and mitigation strategies related to this vulnerability.

Description

An issue was discovered in Elspec G5 digital fault recorder versions 1.1.4.15 and before. A hardcoded backdoor session ID exists that can be used for further access to the device, including reconfiguration tasks.

Impact

The primary impact of CVE-2024-22083 is unauthorized remote access to Elspec G5 digital fault recorders, enabling attackers to reconfigure devices without legitimate credentials. This can lead to operational disruptions in electrical power monitoring and fault diagnostics, potentially causing delayed fault detection or incorrect system responses. While confidentiality impact is low, the availability and integrity of device functions are at risk, which can affect the reliability of power grid operations. In critical infrastructure environments, such disruptions could cascade, impacting broader grid stability and safety. The ease of exploitation (no authentication or user interaction required) increases the risk of attacks, especially in networks where these devices are exposed or insufficiently segmented. Although no known exploits are currently active in the wild, the existence of a hardcoded backdoor is a significant security weakness that could be leveraged by threat actors targeting industrial control systems or critical infrastructure. Organizations relying on these devices may face increased risk of sabotage, espionage, or service disruption.

References

elspec-ltd.com/support/security-advisories/ (opens in a new tab)

Community reviews

Loading reviews…