CVE-2024-41435VulnerabilityPublished 3 Sep 2024

CVE-2024-41435: yugabyte-db · n/a

Affects yugabyte-dbSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

7.5High

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

EPSS: 0.5% chance of exploitation in 30 days – higher than 43% 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:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
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: 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: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within 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 3 Sep 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 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

Affected software

Product	Affected	Fixed in
GitHubyugabyte/yugabyte-db`pkg:github/yugabyte/yugabyte-db`Other threats	Affected =2.21.1.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediately restrict network access to YugabyteDB instances by implementing firewall rules or network segmentation to limit exposure to trusted hosts only. 2. Monitor database logs and network traffic for anomalous or unusually large 'insert into' queries that could indicate exploitation attempts. 3. Employ Web Application Firewalls (WAFs) or database proxies capable of detecting and blocking malformed SQL statements targeting the insert parameter. 4. Engage with YugabyteDB vendor channels and security advisories to obtain and apply patches or updates as soon as they become available. 5. Consider deploying runtime application self-protection (RASP) or intrusion prevention systems (IPS) that can detect buffer overflow attempts at the application or network layer. 6. Conduct regular security assessments and fuzz testing on database inputs to identify similar vulnerabilities proactively. 7. If possible, implement query parameterization and input validation at the application level to reduce the risk of malformed queries reaching the database engine. 8. Prepare incident response plans to quickly recover from potential DoS attacks caused by this vulnerability.

Description

YugabyteDB v2.21.1.0 was discovered to contain a buffer overflow via the "insert into" parameter.

Impact

The primary impact of CVE-2024-41435 is a denial of service (DoS) condition against YugabyteDB instances, potentially causing database crashes and service outages. This can disrupt business operations, especially for organizations relying on YugabyteDB for critical transactional or analytical workloads. Since the vulnerability does not affect confidentiality or integrity, data leakage or unauthorized data modification is not a direct concern. However, availability loss can lead to significant operational and financial consequences, including downtime, loss of customer trust, and cascading failures in dependent systems. The ease of exploitation without authentication or user interaction increases the risk of widespread attacks, particularly in environments where YugabyteDB is exposed to untrusted networks. Organizations with cloud deployments or multi-tenant environments may face amplified risks due to shared infrastructure. The absence of known exploits in the wild provides a window for proactive defense, but the high CVSS score (7.5) underscores the urgency of addressing this vulnerability.

CWE-120Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #11
The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
OWASP Cheat Sheets
Docker Security (opens in a new tab)
XML Security (opens in a new tab)
OWASP ASVS 4.0.3
V5.4.1 (opens in a new tab)
V14.1.2 (opens in a new tab)
V13.3.1 (opens in a new tab)
Attack patterns
Buffer Overflow via Environment Variables (opens in a new tab)
Overflow Buffers (opens in a new tab)
Client-side Injection-induced Buffer Overflow (opens in a new tab)
Filter Failure through Buffer Overflow (opens in a new tab)
MIME Conversion (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Feb 2026, 07:02 UTC

WeaknessesCWE-120

Technical details

References

Community reviews

Related threats