VulnerabilityPublished 17 Jan 2025

CVE-2024-52870: Teradata Vantage Editor · Missing Initialization of Resource

Source CVE Database V5

Not known to be exploited · CVSS 7.1 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

7.1High

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

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

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

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

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

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Jan 2025
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-52870, organizations should implement several specific measures beyond generic advice: 1) Restrict access to Teradata Vantage Editor 1.0.1 to trusted users only, minimizing exposure to untrusted or potentially malicious users. 2) Disable or restrict access to Chromium Developer Tools within the application if possible, or use application-level controls to prevent navigation to arbitrary remote websites. 3) Monitor network traffic originating from endpoints running the editor for unusual or unauthorized connections to external sites, employing network intrusion detection systems (NIDS) or web proxy logs. 4) Enforce strict endpoint security controls, including application whitelisting and user privilege restrictions, to reduce the risk of local exploitation. 5) Educate users about the risks of interacting with unexpected prompts or developer tools within the editor. 6) Engage with Teradata support or security advisories to obtain patches or updates as soon as they become available. 7) Consider isolating the editor environment in a sandbox or virtual machine to contain potential exploitation. 8) Regularly audit and review database access logs for signs of unauthorized queries or data manipulation. These targeted steps can reduce the likelihood and impact of exploitation until an official patch is released.

Description

Teradata Vantage Editor 1.0.1 is mostly intended for SQL database access and docs.teradata.com access, but provides unintended functionality (including Chromium Developer Tools) that can result in a client user accessing arbitrary remote websites.

Impact

The primary impact of CVE-2024-52870 is the potential compromise of confidentiality and integrity within environments using Teradata Vantage Editor 1.0.1. By enabling access to arbitrary remote websites through Chromium Developer Tools, an attacker or malicious user could exfiltrate sensitive data, inject malicious scripts, or manipulate SQL queries or database content indirectly. This could lead to unauthorized data disclosure, data tampering, or the introduction of further malware or exploits via remote content. Since the vulnerability requires local access and user interaction, the risk is somewhat mitigated against remote attackers but remains significant for insider threats or compromised endpoints. Organizations relying on Teradata Vantage Editor for critical data analytics and warehousing could face data breaches, regulatory compliance violations, and operational disruptions. The lack of current known exploits reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits once the vulnerability is public. The absence of a patch increases exposure duration. Overall, the vulnerability poses a high risk to data confidentiality and integrity in affected environments.

CWE-909Missing Initialization of Resource (opens in a new tab)
Class weaknessLikelihood of exploit: Medium
The product does not initialize a critical resource.
Implementation
Explicitly initialize the resource before use. If this is performed through an API function or standard procedure, follow all specified steps.
Implementation
Pay close attention to complex conditionals that affect initialization, since some branches might not perform the initialization.
Implementation
Avoid race conditions (CWE-362) during initialization routines.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 26 Feb 2026, 01:39 UTC

WeaknessesCWE-909

Technical details

References

Community reviews

Related threats