Skip to main content
CVE-2024-51072VulnerabilityPublished Updated

CVE-2024-51072: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Nov 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

AI-suggested

1. Restrict physical and network access to the vehicle's diagnostic interfaces, especially the UDS protocol endpoints, by implementing strict access controls and secure storage of diagnostic tools. 2. Employ network segmentation within the vehicle's internal network (CAN bus or Ethernet) to isolate the instrument cluster ECU from external or less trusted components. 3. Monitor vehicle diagnostic communication for unusual ECUReset requests or repeated reset attempts that could indicate exploitation attempts. 4. Coordinate with KIA and authorized dealers to stay informed about any forthcoming firmware updates or patches addressing this vulnerability. 5. For fleet operators, implement policies to control and log all maintenance and diagnostic activities to detect unauthorized access. 6. Consider additional physical security measures to prevent unauthorized access to the vehicle's OBD-II port or telematics units. 7. Engage with automotive cybersecurity specialists to assess the risk in the specific operational environment and develop tailored detection and response strategies. 8. Advocate for future ECU and UDS protocol implementations to enforce authentication and authorization on critical diagnostic services such as ECUReset to prevent unauthenticated resets.

Description

An issue in KIA Seltos vehicle instrument cluster with software and hardware v1.0 allows attackers to cause a Denial of Service (DoS) via ECU reset UDS service. NOTE: this is disputed by the Supplier because the findings came from a potentially unrealistic test environment (an isolated ECU part that was not in a vehicle), and because the ECUReset specification does not allow a manufacturer to require SecurityAccess and Authentication.

References

Community reviews

Loading reviews…