CVE-2025-29087
Description
A flaw was found in SQLite. This vulnerability allows an attacker to cause an integer overflow via the concat_ws function.
Statement
The severity of this vulnerability is rated as Moderate, despite the potential for a severe outcome in unrestricted environments, primarily due to the limited impact observed within typical product deployments and the strong defense layers in regulated systems. The underlying flaw is a software error identified as CWE-190: Integer Overflow or Wraparound , which, when triggered, can corrupt memory and potentially lead to a complete compromise of system availability. However, a critical factor in the Moderate rating is that Red Hat’s product impact assessment determined that the vulnerability is limited to a Denial of Service (DoS) outcome, preventing Confidentiality or Integrity compromise. Furthermore, regulated environments introduce multiple significant barriers: process isolation ensures that any memory corruption is contained within the single affected process; least functionality reduces the initial attack surface; and layered memory protection mechanisms like Data Execution Prevention (DEP) and Address Space Layout Randomization (ASLR) enhance system resilience against memory manipulation attacks. These controls collectively make successful exploitation difficult, contain the damage to a service crash, and justify the Moderate rating instead of the upstream High score.
RHEL/UBI 9 ships SQLite version 3.34.1, which is not affected by this CVE.This vulnerability only exists in SQLite versions 3.44.0 through 3.49.0.
Red Hat evaluated the vulnerability according to our standard product impact assessment criteria and determined that the issue does not meet the threshold for a High severity rating. Although the upstream advisory scored the issue as High based on potential impact, exploitation requires specific conditions and is limited in scope within Red Hat products. Even if triggered, the vulnerability is limited to a denial-of-service outcome rather than remote code execution or compromise of confidentiality or integrity. For this reason, Red Hat assigned a Moderate severity rating.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.5 | 7.5 | 3.2 |
| Attack Vector | Local | Network | Local |
| Attack Complexity | Low | Low | High |
| Privileges Required | Low | None | None |
| User Interaction | None | None | None |
| Scope | Unchanged | Unchanged | Changed |
| Confidentiality | None | None | None |
| Integrity Impact | None | None | None |
| Availability Impact | High | High | Low |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
cve.org: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:N/I:N/A:L
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (Memory); DoS: Instability
This weakness can generally lead to undefined behavior and therefore crashes. When the calculated result is used for resource allocation, this weakness can cause too many (or too few) resources to be allocated, possibly enabling crashes if the product requests more resources than can be provided.
Integrity
Technical Impact: Modify Memory
If the value in question is important to data (as opposed to flow), simple data corruption has occurred. Also, if the overflow/wraparound results in other conditions such as buffer overflows, further memory corruption may occur.
Confidentiality,Availability,Access Control
Technical Impact: Execute Unauthorized Code or Commands; Bypass Protection Mechanism
This weakness can sometimes trigger buffer overflows, which can be used to execute arbitrary code. This is usually outside the scope of the product's implicit security policy.
Availability,Other
Technical Impact: Alter Execution Logic; DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU)
If the overflow/wraparound occurs in a loop index variable, this could cause the loop to terminate at the wrong time - too early, too late, or not at all (i.e., infinite loops). With too many iterations, some loops could consume too many resources such as memory, file handles, etc., possibly leading to a crash or other DoS.
Access Control
Technical Impact: Bypass Protection Mechanism
If integer values are used in security-critical decisions, such as calculating quotas or allocation limits, integer overflows can be used to cause an incorrect security decision.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
