| 1 |
<!DOCTYPE html> |
| 2 |
<html><head> |
| 3 |
<meta name="viewport" content="width=device-width, initial-scale=1.0"> |
| 4 |
<meta http-equiv="content-type" content="text/html; charset=UTF-8"> |
| 5 |
<link href="sqlite.css" rel="stylesheet"> |
| 6 |
<title>Vulnerabilities</title> |
| 7 |
<!-- path= --> |
| 8 |
</head> |
| 9 |
<body> |
| 10 |
<div class=nosearch> |
| 11 |
<a href="index.html"> |
| 12 |
<img class="logo" src="images/sqlite370_banner.svg" alt="SQLite" border="0"> |
| 13 |
</a> |
| 14 |
<div><!-- IE hack to prevent disappearing logo --></div> |
| 15 |
<div class="tagline desktoponly"> |
| 16 |
Small. Fast. Reliable.<br>Choose any three. |
| 17 |
</div> |
| 18 |
<div class="menu mainmenu"> |
| 19 |
<ul> |
| 20 |
<li><a href="index.html">Home</a> |
| 21 |
<li class='mobileonly'><a href="javascript:void(0)" onclick='toggle_div("submenu")'>Menu</a> |
| 22 |
<li class='wideonly'><a href='about.html'>About</a> |
| 23 |
<li class='desktoponly'><a href="docs.html">Documentation</a> |
| 24 |
<li class='desktoponly'><a href="download.html">Download</a> |
| 25 |
<li class='wideonly'><a href='copyright.html'>License</a> |
| 26 |
<li class='desktoponly'><a href="support.html">Support</a> |
| 27 |
<li class='desktoponly'><a href="prosupport.html">Purchase</a> |
| 28 |
<li class='search' id='search_menubutton'> |
| 29 |
<a href="javascript:void(0)" onclick='toggle_search()'>Search</a> |
| 30 |
</ul> |
| 31 |
</div> |
| 32 |
<div class="menu submenu" id="submenu"> |
| 33 |
<ul> |
| 34 |
<li><a href='about.html'>About</a> |
| 35 |
<li><a href='docs.html'>Documentation</a> |
| 36 |
<li><a href='download.html'>Download</a> |
| 37 |
<li><a href='support.html'>Support</a> |
| 38 |
<li><a href='prosupport.html'>Purchase</a> |
| 39 |
</ul> |
| 40 |
</div> |
| 41 |
<div class="searchmenu" id="searchmenu"> |
| 42 |
<form method="GET" action="search"> |
| 43 |
<select name="s" id="searchtype"> |
| 44 |
<option value="d">Search Documentation</option> |
| 45 |
<option value="c">Search Changelog</option> |
| 46 |
</select> |
| 47 |
<input type="text" name="q" id="searchbox" value=""> |
| 48 |
<input type="submit" value="Go"> |
| 49 |
</form> |
| 50 |
</div> |
| 51 |
</div> |
| 52 |
<script> |
| 53 |
function toggle_div(nm) { |
| 54 |
var w = document.getElementById(nm); |
| 55 |
if( w.style.display=="block" ){ |
| 56 |
w.style.display = "none"; |
| 57 |
}else{ |
| 58 |
w.style.display = "block"; |
| 59 |
} |
| 60 |
} |
| 61 |
function toggle_search() { |
| 62 |
var w = document.getElementById("searchmenu"); |
| 63 |
if( w.style.display=="block" ){ |
| 64 |
w.style.display = "none"; |
| 65 |
} else { |
| 66 |
w.style.display = "block"; |
| 67 |
setTimeout(function(){ |
| 68 |
document.getElementById("searchbox").focus() |
| 69 |
}, 30); |
| 70 |
} |
| 71 |
} |
| 72 |
function div_off(nm){document.getElementById(nm).style.display="none";} |
| 73 |
window.onbeforeunload = function(e){div_off("submenu");} |
| 74 |
/* Disable the Search feature if we are not operating from CGI, since */ |
| 75 |
/* Search is accomplished using CGI and will not work without it. */ |
| 76 |
if( !location.origin || !location.origin.match || !location.origin.match(/http/) ){ |
| 77 |
document.getElementById("search_menubutton").style.display = "none"; |
| 78 |
} |
| 79 |
/* Used by the Hide/Show button beside syntax diagrams, to toggle the */ |
| 80 |
function hideorshow(btn,obj){ |
| 81 |
var x = document.getElementById(obj); |
| 82 |
var b = document.getElementById(btn); |
| 83 |
if( x.style.display!='none' ){ |
| 84 |
x.style.display = 'none'; |
| 85 |
b.innerHTML='show'; |
| 86 |
}else{ |
| 87 |
x.style.display = ''; |
| 88 |
b.innerHTML='hide'; |
| 89 |
} |
| 90 |
return false; |
| 91 |
} |
| 92 |
var antiRobot = 0; |
| 93 |
function antiRobotGo(){ |
| 94 |
if( antiRobot!=3 ) return; |
| 95 |
antiRobot = 7; |
| 96 |
var j = document.getElementById("mtimelink"); |
| 97 |
if(j && j.hasAttribute("data-href")) j.href=j.getAttribute("data-href"); |
| 98 |
} |
| 99 |
function antiRobotDefense(){ |
| 100 |
document.body.onmousedown=function(){ |
| 101 |
antiRobot |= 2; |
| 102 |
antiRobotGo(); |
| 103 |
document.body.onmousedown=null; |
| 104 |
} |
| 105 |
document.body.onmousemove=function(){ |
| 106 |
antiRobot |= 2; |
| 107 |
antiRobotGo(); |
| 108 |
document.body.onmousemove=null; |
| 109 |
} |
| 110 |
setTimeout(function(){ |
| 111 |
antiRobot |= 1; |
| 112 |
antiRobotGo(); |
| 113 |
}, 100) |
| 114 |
antiRobotGo(); |
| 115 |
} |
| 116 |
antiRobotDefense(); |
| 117 |
</script> |
| 118 |
<div class=fancy> |
| 119 |
<div class=nosearch> |
| 120 |
<div class="fancy_title"> |
| 121 |
Vulnerabilities |
| 122 |
</div> |
| 123 |
<details class="fancy_toc"> |
| 124 |
<summary>Table Of Contents</summary> |
| 125 |
<div id="toc_sub"><div class="fancy-toc1"><a href="#executive_summary">1. Executive Summary</a></div> |
| 126 |
<div class="fancy-toc1"><a href="#about_cves">2. About CVEs</a></div> |
| 127 |
<div class="fancy-toc2"><a href="#a_separate_sql_injection_vulnerability_is_usually_required">2.1. A separate SQL injection vulnerability is usually required</a></div> |
| 128 |
<div class="fancy-toc2"><a href="#defense_against_dark_arts">2.2. Defense Against Dark Arts</a></div> |
| 129 |
<div class="fancy-toc2"><a href="#the_sqlite_developer_policy_toward_cves">2.3. The SQLite Developer Policy Toward CVEs</a></div> |
| 130 |
<div class="fancy-toc1"><a href="#status_of_recent_sqlite_cves">3. Status Of Recent SQLite CVEs</a></div> |
| 131 |
</div> |
| 132 |
</details> |
| 133 |
</div> |
| 134 |
|
| 135 |
|
| 136 |
|
| 137 |
|
| 138 |
|
| 139 |
<h1 id="executive_summary"><span>1. </span>Executive Summary</h1> |
| 140 |
|
| 141 |
<ul> |
| 142 |
<li><p> |
| 143 |
CVEs about SQLite probably do not apply to your use of SQLite. |
| 144 |
|
| 145 |
</p></li><li><p> |
| 146 |
All historical vulnerabilities reported against SQLite require at least |
| 147 |
one of these preconditions: |
| 148 |
</p><ol type="1"> |
| 149 |
<li><p> |
| 150 |
The attacker can submit and run arbitrary SQL statements. |
| 151 |
</p></li><li><p> |
| 152 |
The attacker can submit a maliciously crafted database file to the |
| 153 |
application that the application will then open and query. |
| 154 |
</p></li></ol> |
| 155 |
|
| 156 |
</li><li><p> |
| 157 |
Few real-world applications meet either of these preconditions, and hence |
| 158 |
few real-world applications are vulnerable, even if they use older |
| 159 |
and unpatched versions of SQLite. |
| 160 |
|
| 161 |
</p></li><li><p> |
| 162 |
The SQLite development team fixes bugs promptly, |
| 163 |
usually within hours of discovery. New releases of SQLite |
| 164 |
are issued if the bug seems likely to impact real-world |
| 165 |
applications. |
| 166 |
|
| 167 |
</p></li><li><p> |
| 168 |
Grey-hat hackers are rewarded based on the number and severity of |
| 169 |
CVEs that they write. This results in a proliferation of CVEs that |
| 170 |
have minor impact, or no impact at all, but which make |
| 171 |
exaggerated impact claims. |
| 172 |
|
| 173 |
</p></li><li><p><a name="notnew"></a> |
| 174 |
Very few CVEs written about SQLite are real vulnerabilities in the |
| 175 |
sense that they do not give any new capabilities to an attacker. |
| 176 |
Consider: |
| 177 |
</p><ol type="a"> |
| 178 |
<li><p> |
| 179 |
Almost all CVEs written against SQLite require the ability to |
| 180 |
inject and run arbitrary SQL. |
| 181 |
</p></li><li><p> |
| 182 |
The advertised consequence of most CVEs is "denial of service", |
| 183 |
typically by causing a crash through a NULL pointer dereference or |
| 184 |
a division by zero, or similar. |
| 185 |
</p></li><li><p> |
| 186 |
But if an attacker can already run |
| 187 |
arbitrary SQL, they do not need a bug to cause a denial of service. |
| 188 |
There are plenty of perfectly legal and valid SQL statements |
| 189 |
that will consume unlimited CPU, memory, and disk I/O in order |
| 190 |
to create a denial-of-service without requiring help from bugs. |
| 191 |
</p></li><li><p> |
| 192 |
Hence, the mere fact that an attacker has a way to inject and run |
| 193 |
arbitrary SQL is in and of itself a denial-of-service attack. That |
| 194 |
the arbitrary SQL might also tickle a bug in SQLite and cause a |
| 195 |
crash is not a new vulnerability. |
| 196 |
</p></li></ol> |
| 197 |
|
| 198 |
</li><li><p> |
| 199 |
The SQLite developers do not write CVEs. Any CVEs you find on |
| 200 |
SQLite are generated by third-parties, often without any input from the |
| 201 |
core developers. A common scenario is that someone will report a bug in |
| 202 |
SQLite, which will promptly be fixed, then weeks later a CVE for that bug will |
| 203 |
appear, unbeknownst to the developers. |
| 204 |
|
| 205 |
</p></li><li><p> |
| 206 |
You should not assume that a CVE about |
| 207 |
SQLite contains authoritative information. |
| 208 |
CVEs often contain inaccuracies. |
| 209 |
The SQLite developers have attempted to add clarifications and |
| 210 |
corrections to CVEs about SQLite. |
| 211 |
|
| 212 |
</p></li></ul> |
| 213 |
|
| 214 |
<h1 id="about_cves"><span>2. </span>About CVEs</h1> |
| 215 |
|
| 216 |
<p>CVEs ("Common Vulnerabilities and Exposures") are reports of software |
| 217 |
bugs that might allow a system to be hacked. The idea |
| 218 |
behind CVEs is sound. They provide a common naming scheme whereby |
| 219 |
software bugs that might compromise information security can be easily |
| 220 |
tracked. |
| 221 |
|
| 222 |
</p><p>While the original idea behind CVEs is sound, the current processes for |
| 223 |
creating and managing CVEs are inadequate. There are countless grey-hat |
| 224 |
hackers running fuzzers against a wide-variety of open-source software |
| 225 |
products (SQLite as well as many others) and writing up CVEs against |
| 226 |
any problems they find. The grey-hats are rewarded, sometimes with |
| 227 |
prestige and sometimes financially, by the number and severity of |
| 228 |
the CVEs they write. This incentive results in a proliferation |
| 229 |
of CVEs which are often not well-vetted and which can have exaggerated |
| 230 |
impact claims. The quality-control procedures for CVEs are unable |
| 231 |
to cope with this flood of inputs, making it difficult to correct |
| 232 |
exaggerated, misleading, omitted, or inaccurate claims. |
| 233 |
|
| 234 |
</p><p>This is not to say that CVEs are useless. CVEs do still (mostly) |
| 235 |
report actual bugs. But in most cases the bugs are not true vulnerabilities, |
| 236 |
in the sense that they do not contribute to data loss or compromise |
| 237 |
in and of themselves. |
| 238 |
It is good that bugs are reported and fixed. But not every bug is |
| 239 |
accessible from every application. In the case of SQLite, most of the |
| 240 |
bugs reported by CVEs are inaccessible in most applications. Upgrading |
| 241 |
to the latest version of SQLite is always a good plan, but it need not |
| 242 |
be an emergency just because an anonymous grey-hat on the internet |
| 243 |
wrote up a CVE. |
| 244 |
|
| 245 |
</p><h2 id="a_separate_sql_injection_vulnerability_is_usually_required"><span>2.1. </span>A separate SQL injection vulnerability is usually required</h2> |
| 246 |
|
| 247 |
<p> |
| 248 |
Other C-libraries that process complex structured inputs will |
| 249 |
routinely be asked to deal with unvetted inputs from untrusted |
| 250 |
sources. Libraries like libjpeg, or libzip, or OpenSSL are |
| 251 |
handed input streams that come directly from potentially hostile |
| 252 |
agents. |
| 253 |
|
| 254 |
</p><p> |
| 255 |
But database engines like SQLite are usually not this way. |
| 256 |
The SQL scripts that are passed into SQLite come from the |
| 257 |
(trusted) application itself, not from an attacker. Sometimes |
| 258 |
applications contain bugs by which an external attacker can |
| 259 |
trick the application into sending SQL of the attackers design |
| 260 |
into the database engine. This is a separate bug in the |
| 261 |
application called an |
| 262 |
<a href="https://en.wikipedia.org/wiki/SQL_injection">SQL Injection |
| 263 |
vulnerability</a>. Since SQL text is executable code, an |
| 264 |
SQL Injection vulnerability is actually a special case of a |
| 265 |
<a href="https://en.wikipedia.org/wiki/Arbitrary_code_execution">Remote |
| 266 |
Code Execution (RCE) vulnerability</a>. An SQL Injection is perhaps not |
| 267 |
quite as bad as other kinds of RCEs because, |
| 268 |
while SQL is a powerful language, it is not as convenient |
| 269 |
for crafting an exploit as Python or shell script or raw machine code. |
| 270 |
Nevertheless, an SQL Injection is a serious problem. |
| 271 |
|
| 272 |
</p><p> |
| 273 |
Most CVEs written about SQLite assume that the attacker is |
| 274 |
able to run arbitrary SQL scripts in SQLite. In most applications, |
| 275 |
this means that there must first be an SQL Injection vulnerability |
| 276 |
that allows the attacker to inject the malicious SQL. |
| 277 |
|
| 278 |
</p><p> |
| 279 |
A few applications do allow untrusted SQL scripts received from |
| 280 |
potentially hostile agents to be run direct in SQLite. The main |
| 281 |
example of this is the Chrome and Safari web browsers, which allow |
| 282 |
an anonymous web page to run SQL using the WebSQL feature of Javascript. |
| 283 |
This is done inside a sandbox with tightly controlled constraints on |
| 284 |
resources, lest the SQL script try to soak up all available memory |
| 285 |
or CPU cycles in a denial-of-service attack. Chrome and Safari |
| 286 |
have the infrastructure in place to allow a hostile agent to run |
| 287 |
code which does not harm or compromise the rest of the machine. |
| 288 |
They have to, as they also run Javascript which could, if not |
| 289 |
tightly controlled, do even more damage than unrestrained SQL. |
| 290 |
Apart from Chrome and Safari, no applications known to the |
| 291 |
SQLite developers deliberately allows an anonymous remote agent |
| 292 |
to run arbitrary SQL text. |
| 293 |
|
| 294 |
</p><p>However, most CVEs written against SQLite flippantly assume |
| 295 |
that an attacker is free to run any arbitrary SQL in the database |
| 296 |
engine. So to a good approximation, this means most CVEs |
| 297 |
written against SQLite really only apply to SQLite as it is |
| 298 |
used in Chrome and Safari. Or, in other words, most CVEs |
| 299 |
for SQLite do not apply to you unless you are one of the |
| 300 |
developers of Chrome or Safari. |
| 301 |
|
| 302 |
</p><h2 id="defense_against_dark_arts"><span>2.2. </span>Defense Against Dark Arts</h2> |
| 303 |
|
| 304 |
<p> |
| 305 |
Most applications can use SQLite without having to worry about |
| 306 |
bugs in obscure SQL inputs. If the application controls |
| 307 |
the SQL, and the application is not deliberately trying to break |
| 308 |
SQLite, then everything should just work. |
| 309 |
It is not necessary to have the latest patched version of SQLite. |
| 310 |
Any older version should work just fine. |
| 311 |
|
| 312 |
</p><p> |
| 313 |
However, there are some occasions where an application does need |
| 314 |
to be able to safely run untrusted SQL. The SQLite developers work hard |
| 315 |
to make SQLite safe for this purpose, though there are occasional |
| 316 |
slip-ups. It is good to keep up-to-date with the latest patches |
| 317 |
in this case. The separate <a href="security.html">defense against dark arts</a> document |
| 318 |
contains additional suggestions that can help prevent zero-day |
| 319 |
attacks in cases where SQLite is given inputs that come directly |
| 320 |
from untrusted sources. |
| 321 |
|
| 322 |
</p><h2 id="the_sqlite_developer_policy_toward_cves"><span>2.3. </span>The SQLite Developer Policy Toward CVEs</h2> |
| 323 |
|
| 324 |
<p>SQLite developers fix all bugs in SQLite as soon as they are reported, |
| 325 |
usually within a few hours. The fixes are immediately available on the |
| 326 |
<a href="https://sqlite.org/src/timeline">public SQLite source tree</a>. |
| 327 |
If a bug seems like it might cause problems for existing applications, |
| 328 |
a new patch release for SQLite will be issued. |
| 329 |
|
| 330 |
</p><p>However, the SQLite developers do not track CVEs. There are |
| 331 |
various reasons for this: |
| 332 |
|
| 333 |
</p><ol> |
| 334 |
<li><p> |
| 335 |
The developers often do not find out about CVEs until long after the |
| 336 |
bug is fixed. You can see this by the fact that many CVEs reference the |
| 337 |
bug fix in their initial report. |
| 338 |
|
| 339 |
</p></li><li><p> |
| 340 |
CVEs are a low-quality source of information about bugs in SQLite |
| 341 |
that are likely to affect most applications. |
| 342 |
|
| 343 |
</p></li><li><p> |
| 344 |
Almost all bugs reported by CVEs are just bugs and not |
| 345 |
true vulnerabilities. Claiming that they are vulnerabilities is |
| 346 |
stretching the meaning of the word "vulnerability" and the SQLite |
| 347 |
developers do not wish to participate in that deception. |
| 348 |
|
| 349 |
</p></li><li><p> |
| 350 |
The developers have no editorial influence on the content of CVEs, |
| 351 |
and they do not like to be controlled by groups in which they have |
| 352 |
no voice. |
| 353 |
</p></li></ol> |
| 354 |
|
| 355 |
|
| 356 |
<a name="cvetab"></a> |
| 357 |
|
| 358 |
<h1 id="status_of_recent_sqlite_cves"><span>3. </span>Status Of Recent SQLite CVEs</h1> |
| 359 |
|
| 360 |
<p>Though the SQLite developers do not consider CVEs to be a reliable |
| 361 |
source of information about bugs in SQLite, they recognize that many |
| 362 |
groups, and especially small teams working at the bottom of tall |
| 363 |
bureaucracies, sometimes need to track CVEs, whether they are useful |
| 364 |
or not. To aid in this chore, the following table of recent CVEs |
| 365 |
affecting SQLite is provided. |
| 366 |
|
| 367 |
</p><p>If you notice new CVEs associated with SQLite that are not in |
| 368 |
the table below, please bring them to the attention of the developers |
| 369 |
on the <a href="https://sqlite.org/forum/about">SQLite Forum</a> so they can |
| 370 |
be added. |
| 371 |
|
| 372 |
</p><table border="1" cellpadding="5" cellspacing="0" style="margin-left:5ex;"> |
| 373 |
<thead> |
| 374 |
<tr> |
| 375 |
<th valign="bottom">CVE Number</th> |
| 376 |
<th valign="bottom">Fix</th> |
| 377 |
<th valign="bottom">Comments</th> |
| 378 |
</tr> |
| 379 |
</thead> |
| 380 |
<tbody> |
| 381 |
|
| 382 |
<tr><td valign='top'> |
| 383 |
<a id='CVE-2025-3277'></a> |
| 384 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2025-3277'>CVE-2025-3277</a> |
| 385 |
</td> |
| 386 |
<td valign='top'><a href="releaselog/3_49_1.html">3.49.1</a><br>(2025-02-18)</td> |
| 387 |
<td valign='top'>A bug in the <a href="lang_corefunc.html#concat_ws">concat_ws() SQL function</a> can cause a write past the end of an array |
| 388 |
obtained from malloc(). If an attacker can control the first argument to concat_ws(), |
| 389 |
so that the separator string is large - more than 2MB - then an integer overflow |
| 390 |
in the calculation of the size of the result buffer might cause a short malloc() and |
| 391 |
subsequent write past the end of the allocated space. Fixed by |
| 392 |
<a href="https://sqlite.org/src/info/2025-02-16T10:57z">check-in 2025-02-16T10:57z</a>.</td> |
| 393 |
</tr> |
| 394 |
|
| 395 |
<tr><td valign='top'> |
| 396 |
<a id='CVE-2025-6965'></a> |
| 397 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2025-6965'>CVE-2025-6965</a> |
| 398 |
</td> |
| 399 |
<td valign='top'><a href="releaselog/3_50_2.html">3.50.2</a><br>(2025-06-28)</td> |
| 400 |
<td valign='top'>An attacker who can inject arbitrary SQL statements into an application |
| 401 |
might be able to cause an integer overflow resulting in a read off the end |
| 402 |
of an array. |
| 403 |
<a href="https://sqlite.org/src/info/5508b56fd24016c1">Fixed on 2025-06-27</a>.</td> |
| 404 |
</tr> |
| 405 |
|
| 406 |
<tr><td valign='top'> |
| 407 |
<a id='CVE-2025-7458'></a> |
| 408 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2025-7458'>CVE-2025-7458</a> |
| 409 |
</td> |
| 410 |
<td valign='top'><a href="releaselog/3_42_0.html">3.42.0</a><br>(2023-05-16)</td> |
| 411 |
<td valign='top'>An attacker who can inject arbitrary SQL statements into an application |
| 412 |
might be able to cause an integer overflow resulting in a read off the end |
| 413 |
of an array. |
| 414 |
<a href="https://sqlite.org/src/info/12ad822d9b827777">Fixed on 2023-03-16</a>.</td> |
| 415 |
</tr> |
| 416 |
|
| 417 |
<tr><td valign='top'> |
| 418 |
<a id='CVE-2025-7709'></a> |
| 419 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2025-7709'>CVE-2025-7709</a> |
| 420 |
</td> |
| 421 |
<td valign='top'><a href="releaselog/3_50_3.html">3.50.3</a><br>(2025-07-17)</td> |
| 422 |
<td valign='top'>An attacker who has complete control over the database content could |
| 423 |
create a corrupt <a href="fts5.html">FTS5</a> index resulting access to memory outside the |
| 424 |
bounds of an array due to integer overflow. |
| 425 |
<a href="https://sqlite.org/src/info/63595b74956a9391">Fixed on 2025-07-15</a>.</td> |
| 426 |
</tr> |
| 427 |
|
| 428 |
<tr><td valign='top'> |
| 429 |
<a id='CVE-2025-29087'></a> |
| 430 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2025-29087'>CVE-2025-29087</a> |
| 431 |
</td> |
| 432 |
<td valign='top'><a href="releaselog/3_49_1.html">3.49.1</a><br>(2025-02-18)</td> |
| 433 |
<td valign='top'>Duplicate of <a href="https://nvd.nist.gov/vuln/detail/CVE-2025-3277">CVE-2025-3277</a></td> |
| 434 |
</tr> |
| 435 |
|
| 436 |
<tr><td valign='top'> |
| 437 |
<a id='CVE-2025-29088'></a> |
| 438 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2025-29088'>CVE-2025-29088</a> |
| 439 |
</td> |
| 440 |
<td valign='top'><a href="releaselog/3_49_1.html">3.49.1</a><br>(2025-02-18)</td> |
| 441 |
<td valign='top'>Passing out-of-bounds arguments to the C-language API routine |
| 442 |
<a href="c3ref/db_config.html">sqlite3_db_config</a>(db,<a href="c3ref/c_dbconfig_defensive.html#sqlitedbconfiglookaside">SQLITE_DBCONFIG_LOOKASIDE</a>,...) can lead |
| 443 |
to a crash and denial of service. Reported by |
| 444 |
<a href="https://sqlite.org/forum/forumpost/48f365daec">Forum post 48f365daec</a>. |
| 445 |
Complaint addressed by |
| 446 |
<a href="https://sqlite.org/src/info/202502171416Z">check-in 2025-02-17T14:16Z</a>.</td> |
| 447 |
</tr> |
| 448 |
|
| 449 |
<tr><td valign='top'> |
| 450 |
<a id='CVE-2025-52099'></a> |
| 451 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2025-52099'>CVE-2025-52099</a> |
| 452 |
</td> |
| 453 |
<td valign='top'><a href="releaselog/3_49_1.html">3.49.1</a><br>(2025-02-18)</td> |
| 454 |
<td valign='top'>Duplicate of <a href="https://nvd.nist.gov/vuln/detail/CVE-2025-29088">CVE-2025-29088</a></td> |
| 455 |
</tr> |
| 456 |
|
| 457 |
<tr><td valign='top'> |
| 458 |
<a id='CVE-2025-70873'></a> |
| 459 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2025-70873'>CVE-2025-70873</a> |
| 460 |
</td> |
| 461 |
<td valign='top'><a href="releaselog/3_52_0.html">3.52.0</a><br>(2026-03-06)</td> |
| 462 |
<td valign='top'>When using the <a href="zipfile.html">zipfile extension</a> (not a part of standard SQLite but usually |
| 463 |
included in builds of the <a href="cli.html">CLI</a>), a malformed ZIP file input can result in an out-of-bounds read. |
| 464 |
Reported by <a href="https://sqlite.org/forum/forumpost/761eac3c82">forum post 2025-12-06T16:46:32Z</a> |
| 465 |
and fixed in trunk by |
| 466 |
<a href="https://sqlite.org/src/info/9766b47beb9ec72f">check-in 2025-12-06T23:58:09.413Z</a>.</td> |
| 467 |
</tr> |
| 468 |
|
| 469 |
<tr><td valign='top'> |
| 470 |
<a id='CVE-2024-0232'></a> |
| 471 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2024-0232'>CVE-2024-0232</a> |
| 472 |
</td> |
| 473 |
<td valign='top'><a href="releaselog/3_43_2.html">3.43.2</a><br>(2023-10-10)</td> |
| 474 |
<td valign='top'>An attacker who can inject arbitrary SQL statements into an application |
| 475 |
might be able to provoke a use-after-free bug in SQLite's JSON parser that |
| 476 |
can (in theory) lead to an application crash and denial of service. See |
| 477 |
<a href="https://sqlite.org/forum/forumpost/b25edc1d4662ebca">forum thread b25edc1d4662</a> |
| 478 |
for the bug report.</td> |
| 479 |
</tr> |
| 480 |
|
| 481 |
<tr><td valign='top'> |
| 482 |
<a id='CVE-2023-32697'></a> |
| 483 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2023-32697'>CVE-2023-32697</a> |
| 484 |
</td> |
| 485 |
<td valign='top'>Not a bug in SQLite</td> |
| 486 |
<td valign='top'>This is a bug in the SQLite JDBC library, which is a wrapper library that |
| 487 |
provides access to SQLite from Java. SQLite JDBC is created and maintained |
| 488 |
independently from SQLite. Despite the use of "SQLite" in the name, the |
| 489 |
SQLite JDBC library is not affiliated with the SQLite project in any way. |
| 490 |
The vulnerability identified by this CVE is in the separate SQLite JDBC |
| 491 |
wrapper library and does not affect SQLite itself.</td> |
| 492 |
</tr> |
| 493 |
|
| 494 |
<tr><td valign='top'> |
| 495 |
<a id='CVE-2023-39939'></a> |
| 496 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2023-39939'>CVE-2023-39939</a> |
| 497 |
</td> |
| 498 |
<td valign='top'>Not a bug in SQLite</td> |
| 499 |
<td valign='top'>This is not a bug in SQLite. This is an |
| 500 |
<a href="https://en.wikipedia.org/wiki/SQL_injection">SQL injection bug</a> in an application |
| 501 |
(LuxCal Web Calendar) that links against SQLite. |
| 502 |
Even though this CVE is not about SQLite, "SQLite" is |
| 503 |
mentioned in the description and so we list it here.</td> |
| 504 |
</tr> |
| 505 |
|
| 506 |
<tr><td valign='top'> |
| 507 |
<a id='CVE-2023-39543'></a> |
| 508 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2023-39543'>CVE-2023-39543</a> |
| 509 |
</td> |
| 510 |
<td valign='top'>Not a bug in SQLite</td> |
| 511 |
<td valign='top'>This is not a bug in SQLite. This is an |
| 512 |
<a href="https://developer.mozilla.org/en-US/docs/Glossary/Cross-site_scripting">XSS vulnerability</a> |
| 513 |
in a separate application (LuxCal Web Calendar) that links against |
| 514 |
SQLite. The bug is in the application, not in SQLite. However "SQLite" is |
| 515 |
mentioned in the description and so we list it here.</td> |
| 516 |
</tr> |
| 517 |
|
| 518 |
<tr><td valign='top'> |
| 519 |
<a id='CVE-2023-7104'></a> |
| 520 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2023-7104'>CVE-2023-7104</a> |
| 521 |
</td> |
| 522 |
<td valign='top'><a href="releaselog/3_43_1.html">3.43.1</a><br>(2023-09-11)</td> |
| 523 |
<td valign='top'>This is a bug in the <a href="sessionintro.html">session extension</a> of SQLite, not in the SQLite core. |
| 524 |
This bug is only reachable by applications that recompile SQLite using the |
| 525 |
<a href="compile.html#enable_session">-DSQLITE_ENABLE_SESSION</a> compile-time option and then use the Session |
| 526 |
C-language APIs to process a <a href="sessionintro.html#changeset">changeset</a> that has been subtly corrupted by an |
| 527 |
adversary. So this bug probably does not apply to you. See |
| 528 |
<a href="https://sqlite.org/forum/forumpost/f935c4708dd528d9">forum post f935c4708dd528d9</a> |
| 529 |
for additional information.</td> |
| 530 |
</tr> |
| 531 |
|
| 532 |
<tr><td valign='top'> |
| 533 |
<a id='CVE-2022-46908'></a> |
| 534 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2022-46908'>CVE-2022-46908</a> |
| 535 |
</td> |
| 536 |
<td valign='top'>Not a bug in the core SQLite library</td> |
| 537 |
<td valign='top'>This is a bug in the --safe command-line option of the <a href="cli.html">command-line shell</a> |
| 538 |
program that is available for accessing SQLite database files. The bug does |
| 539 |
not exist in the SQLite library. Nor is it an issue for the <a href="cli.html">CLI</a> as long as |
| 540 |
the user does not depend on the --safe option. It is not serious. It is |
| 541 |
debatable whether or not this is a security issue.</td> |
| 542 |
</tr> |
| 543 |
|
| 544 |
<tr><td valign='top'> |
| 545 |
<a id='CVE-2022-38627'></a> |
| 546 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2022-38627'>CVE-2022-38627</a> |
| 547 |
</td> |
| 548 |
<td valign='top'>Not a bug in SQLite</td> |
| 549 |
<td valign='top'>This is not a bug in SQLite. This is an |
| 550 |
<a href="https://en.wikipedia.org/wiki/SQL_injection">SQL injection bug</a> in a specific |
| 551 |
PHP application. In other words, the bug is in the PHP application code, not |
| 552 |
in SQLite. Even though this CVE is not about SQLite, "SQLite" is |
| 553 |
mentioned in the publicity about the bug and so we list it here.</td> |
| 554 |
</tr> |
| 555 |
|
| 556 |
<tr><td valign='top'> |
| 557 |
<a id='CVE-2022-35737'></a> |
| 558 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2022-35737'>CVE-2022-35737</a> |
| 559 |
</td> |
| 560 |
<td valign='top'><a href="releaselog/3_39_2.html">3.39.2</a><br>(2022-07-21)</td> |
| 561 |
<td valign='top'>This bug is an array-bounds overflow. The bug is only accessible when using some |
| 562 |
of the C-language APIs provided by SQLite. The bug cannot be reached using SQL |
| 563 |
nor can it be reached by providing SQLite with a corrupt database file. |
| 564 |
The bug only comes up when very long string inputs (greater than 2 billion bytes |
| 565 |
in length) are provided as arguments to a few specific C-language interfaces, |
| 566 |
and even then only under special circumstances.</td> |
| 567 |
</tr> |
| 568 |
|
| 569 |
<tr><td valign='top'> |
| 570 |
<a id='CVE-2022-24854'></a> |
| 571 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2022-24854'>CVE-2022-24854</a> |
| 572 |
</td> |
| 573 |
<td valign='top'>Not a bug in SQLite</td> |
| 574 |
<td valign='top'>This CVE describes a bug in an application that uses SQLite, not in SQLite itself. |
| 575 |
SQLite is doing everything correctly. The application grants users the ability to |
| 576 |
run SQL statements, using SQLite, that can leak or change information that those users |
| 577 |
should not normally have access to. This is purely an application bug. It does not |
| 578 |
describe a malfunction or vulnerability in SQLite.</td> |
| 579 |
</tr> |
| 580 |
|
| 581 |
<tr><td valign='top'> |
| 582 |
<a id='CVE-2022-21227'></a> |
| 583 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2022-21227'>CVE-2022-21227</a> |
| 584 |
</td> |
| 585 |
<td valign='top'>Not a bug in SQLite</td> |
| 586 |
<td valign='top'>This CVE describes a bug in a third-party packages that provides a binding |
| 587 |
for SQLite to Node.js. The bug reported is in the third-party Node.js binding, |
| 588 |
not in SQLite itself. Do not be confused by the use of the word "SQLite" in the |
| 589 |
ambiguously-worded CVE description.</td> |
| 590 |
</tr> |
| 591 |
|
| 592 |
<tr><td valign='top'> |
| 593 |
<a id='CVE-2021-45346'></a> |
| 594 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2021-45346'>CVE-2021-45346</a> |
| 595 |
</td> |
| 596 |
<td valign='top'>Not a bug in SQLite</td> |
| 597 |
<td valign='top'>This CVE is misinformation. See the discussion around |
| 598 |
<a href="https://sqlite.org/forum/forumpost/53de8864ba114bf6">SQLite forum post 53de8864ba114bf</a>.</td> |
| 599 |
</tr> |
| 600 |
|
| 601 |
<tr><td valign='top'> |
| 602 |
<a id='CVE-2021-42169'></a> |
| 603 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2021-42169'>CVE-2021-42169</a> |
| 604 |
</td> |
| 605 |
<td valign='top'>Not a bug in SQLite</td> |
| 606 |
<td valign='top'>This CVE has nothing whatsoever to do with SQLite. It is about a bug in |
| 607 |
application that happens to use SQLite. Since SQLite is mentioned in the |
| 608 |
CVE description, the CVE is included here to emphasize that |
| 609 |
this is not an SQLite bug.</td> |
| 610 |
</tr> |
| 611 |
|
| 612 |
<tr><td valign='top'> |
| 613 |
<a id='CVE-2021-36690'></a> |
| 614 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2021-36690'>CVE-2021-36690</a> |
| 615 |
</td> |
| 616 |
<td valign='top'>Not a bug in the core SQLite library</td> |
| 617 |
<td valign='top'>This bug is not in the SQLite core library, but rather in an |
| 618 |
<a href="https://sqlite.org/src/dir?ci=trunk&name=ext/expert"> |
| 619 |
experimental extension</a> that is used to implement the |
| 620 |
<a href="cli.html#expert">.expert command</a> in the <a href="cli.html">CLI</a>. The code that contains the bug |
| 621 |
does not appear in <a href="amalgamation.html">standard SQLite builds</a>, though it |
| 622 |
is included in the <a href="cli.html">sqlite3.exe command-line tool</a>. |
| 623 |
Applications must link against the extra source code files that |
| 624 |
implement the extension and take other deliberate actions to |
| 625 |
activate the extension before the troublesome code can be run. |
| 626 |
For the rare application that uses the troublesome extension, |
| 627 |
the consequence of this bug is that malicious SQL can cause a |
| 628 |
NULL pointer deference and denial of service. |
| 629 |
<a href='https://sqlite.org/forum/info/78165fa25061742f'>(details)</a></td> |
| 630 |
</tr> |
| 631 |
|
| 632 |
<tr><td valign='top'> |
| 633 |
<a id='CVE-2021-31239'></a> |
| 634 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2021-31239'>CVE-2021-31239</a> |
| 635 |
</td> |
| 636 |
<td valign='top'>Not a bug in the core SQLite library</td> |
| 637 |
<td valign='top'>This is a bug in the <a href="cli.html">CLI</a>. It allows a user with unrestricted shell access to cause |
| 638 |
a denial-of-service. Of course, there are a million easier ways for a user with |
| 639 |
unrestricted shell access to cause far worse mischief. The problem was in the |
| 640 |
<a href="https://sqlite.org/src/doc/trunk/ext/misc/appendvfs.c">appendvfs extension</a> which |
| 641 |
is not a part of standard SQLite. |
| 642 |
<a href='https://sqlite.org/src/info/04f6439f4d9b9b1f'>(details)</a></td> |
| 643 |
</tr> |
| 644 |
|
| 645 |
<tr><td valign='top'> |
| 646 |
<a id='CVE-2021-28305'></a> |
| 647 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2021-28305'>CVE-2021-28305</a> |
| 648 |
</td> |
| 649 |
<td valign='top'>Not a bug in SQLite</td> |
| 650 |
<td valign='top'>This is not a bug in SQLite. The bug is in a third-party application that |
| 651 |
uses SQLite. SQLite is mentioned by name in the CVE description, |
| 652 |
however, so we have included the CVE in the list.</td> |
| 653 |
</tr> |
| 654 |
|
| 655 |
<tr><td valign='top'> |
| 656 |
<a id='CVE-2021-23404'></a> |
| 657 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2021-23404'>CVE-2021-23404</a> |
| 658 |
</td> |
| 659 |
<td valign='top'>Not a bug in SQLite</td> |
| 660 |
<td valign='top'>This is not a bug in SQLite. The bug is in a third-party application that |
| 661 |
uses SQLite and includes "sqlite" in its name. This CVE is included on the |
| 662 |
list because it mentions SQLite even though the bug has nothing to do |
| 663 |
with SQLite.</td> |
| 664 |
</tr> |
| 665 |
|
| 666 |
<tr><td valign='top'> |
| 667 |
<a id='CVE-2021-20227'></a> |
| 668 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2021-20227'>CVE-2021-20227</a> |
| 669 |
</td> |
| 670 |
<td valign='top'><a href="releaselog/3_34_1.html">3.34.1</a><br>(2021-01-20)</td> |
| 671 |
<td valign='top'>Malicious SQL statement causes read-after-free. No harm can come of this |
| 672 |
particular read-after-free instance, as far as anyone knows. The bug is |
| 673 |
undetectable without a memory sanitizer. The CVE |
| 674 |
claims that this bug is an RCE - a Remote Code Execution |
| 675 |
vulnerability, but that claim is incorrect. |
| 676 |
The RCE claim is misinformation. |
| 677 |
<a href='https://sqlite.org/src/info/30a4c323650cc949'>(details)</a></td> |
| 678 |
</tr> |
| 679 |
|
| 680 |
<tr><td valign='top'> |
| 681 |
<a id='CVE-2021-20223'></a> |
| 682 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2021-20223'>CVE-2021-20223</a> |
| 683 |
</td> |
| 684 |
<td valign='top'><a href="releaselog/3_34_0.html">3.34.0</a><br>(2020-12-01)</td> |
| 685 |
<td valign='top'>The problem identified by this CVE is <u>not</u> a vulnerability. |
| 686 |
It is a malfunction. A coding error causes <a href="fts5.html">FTS5</a> |
| 687 |
to sometimes return inconsistent and incorrect results under obscure circumstances, |
| 688 |
but no memory errors occur. |
| 689 |
<a href='https://sqlite.org/src/info/b7b7bde9b7a03665'>(details)</a></td> |
| 690 |
</tr> |
| 691 |
|
| 692 |
<tr><td valign='top'> |
| 693 |
<a id='CVE-2021-0646'></a> |
| 694 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2021-0646'>CVE-2021-0646</a> |
| 695 |
</td> |
| 696 |
<td valign='top'><a href="releaselog/3_32_1.html">3.32.1</a><br>(2020-05-25)</td> |
| 697 |
<td valign='top'>Duplicate of CVE-2020-13434.</td> |
| 698 |
</tr> |
| 699 |
|
| 700 |
<tr><td valign='top'> |
| 701 |
<a id='CVE-2020-15358'></a> |
| 702 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2020-15358'>CVE-2020-15358</a> |
| 703 |
</td> |
| 704 |
<td valign='top'><a href="releaselog/3_32_3.html">3.32.3</a><br>(2020-06-18)</td> |
| 705 |
<td valign='top'>Malicious SQL statement causes a read past the end of a heap buffer. |
| 706 |
<a href='https://sqlite.org/src/info/8f157e8010b22af0'>(details)</a></td> |
| 707 |
</tr> |
| 708 |
|
| 709 |
<tr><td valign='top'> |
| 710 |
<a id='CVE-2020-13871'></a> |
| 711 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2020-13871'>CVE-2020-13871</a> |
| 712 |
</td> |
| 713 |
<td valign='top'><a href="releaselog/3_32_3.html">3.32.3</a><br>(2020-06-18)</td> |
| 714 |
<td valign='top'>Malicious SQL statement causes a read-only use-after-free memory error. |
| 715 |
<a href='https://sqlite.org/src/info/c8d3b9f0a750a529'>(details)</a></td> |
| 716 |
</tr> |
| 717 |
|
| 718 |
<tr><td valign='top'> |
| 719 |
<a id='CVE-2020-13632'></a> |
| 720 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2020-13632'>CVE-2020-13632</a> |
| 721 |
</td> |
| 722 |
<td valign='top'><a href="releaselog/3_32_0.html">3.32.0</a><br>(2020-05-22)</td> |
| 723 |
<td valign='top'>Malicious SQL statement causes a read of a NULL pointer in the |
| 724 |
<a href="fts3.html#matchinfo">matchinfo()</a> SQL function of the <a href="fts3.html">FTS3</a> extension, resulting in |
| 725 |
denial of service. |
| 726 |
<a href='https://sqlite.org/src/info/a4dd148928ea65bd'>(details)</a></td> |
| 727 |
</tr> |
| 728 |
|
| 729 |
<tr><td valign='top'> |
| 730 |
<a id='CVE-2020-13631'></a> |
| 731 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2020-13631'>CVE-2020-13631</a> |
| 732 |
</td> |
| 733 |
<td valign='top'><a href="releaselog/3_32_0.html">3.32.0</a><br>(2020-05-22)</td> |
| 734 |
<td valign='top'>Malicious SQL statement (an ALTER TABLE that tries to rename a |
| 735 |
<a href="vtab.html">virtual table</a> into one of its own <a href="vtab.html#xshadowname">shadow tables</a>) |
| 736 |
causes an infinite loop and denial of service. |
| 737 |
<a href='https://sqlite.org/src/info/eca0ba2cf4c0fdf7'>(details)</a></td> |
| 738 |
</tr> |
| 739 |
|
| 740 |
<tr><td valign='top'> |
| 741 |
<a id='CVE-2020-13630'></a> |
| 742 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2020-13630'>CVE-2020-13630</a> |
| 743 |
</td> |
| 744 |
<td valign='top'><a href="releaselog/3_32_0.html">3.32.0</a><br>(2020-05-22)</td> |
| 745 |
<td valign='top'>Malicious SQL statement causes a read-only use-after-free, |
| 746 |
possibly resulting in an incorrect output from the <a href="fts3.html#snippet">snippet()</a> |
| 747 |
SQL function of the <a href="fts3.html">FTS3</a> extension. There is no known |
| 748 |
way to exfiltrate data or crash the application using this bug. |
| 749 |
<a href='https://sqlite.org/src/info/0d69f76f0865f962'>(details)</a></td> |
| 750 |
</tr> |
| 751 |
|
| 752 |
<tr><td valign='top'> |
| 753 |
<a id='CVE-2020-13435'></a> |
| 754 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2020-13435'>CVE-2020-13435</a> |
| 755 |
</td> |
| 756 |
<td valign='top'><a href="releaselog/3_32_1.html">3.32.1</a><br>(2020-05-25)</td> |
| 757 |
<td valign='top'>Malicious SQL statement causes a read access to a NULL pointer and |
| 758 |
denial of service. |
| 759 |
<a href='https://sqlite.org/src/info/7a5279a25c57adf1'>(details)</a></td> |
| 760 |
</tr> |
| 761 |
|
| 762 |
<tr><td valign='top'> |
| 763 |
<a id='CVE-2020-13434'></a> |
| 764 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2020-13434'>CVE-2020-13434</a> |
| 765 |
</td> |
| 766 |
<td valign='top'><a href="releaselog/3_32_1.html">3.32.1</a><br>(2020-05-25)</td> |
| 767 |
<td valign='top'>Malicious SQL statement involving the printf() SQL function results |
| 768 |
in an integer overflow which can overwrite the stack with over 2 |
| 769 |
billion bytes of 0x30 or 0x20 (ASCII '0' or ' '). |
| 770 |
Even though this is a stack overwrite, there is no known way to |
| 771 |
redirect control or otherwise escalate the level of harm. |
| 772 |
This is a denial-of-service attack only. |
| 773 |
<a href='https://sqlite.org/src/info/23439ea582241138'>(details)</a></td> |
| 774 |
</tr> |
| 775 |
|
| 776 |
<tr><td valign='top'> |
| 777 |
<a id='CVE-2020-11656'></a> |
| 778 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2020-11656'>CVE-2020-11656</a> |
| 779 |
</td> |
| 780 |
<td valign='top'><a href="releaselog/3_32_0.html">3.32.0</a><br>(2020-05-22)</td> |
| 781 |
<td valign='top'>Malicious SQL statement causes read-only use-after-free of memory allocation |
| 782 |
if SQLite is compile with -DSQLITE_DEBUG. Does not affect release |
| 783 |
builds. |
| 784 |
<a href='https://sqlite.org/src/info/4722bdab08cb1'>(details)</a></td> |
| 785 |
</tr> |
| 786 |
|
| 787 |
<tr><td valign='top'> |
| 788 |
<a id='CVE-2020-11655'></a> |
| 789 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2020-11655'>CVE-2020-11655</a> |
| 790 |
</td> |
| 791 |
<td valign='top'><a href="releaselog/3_32_0.html">3.32.0</a><br>(2020-05-22)</td> |
| 792 |
<td valign='top'>Malicious SQL statement causes a read using an uninitialized pointer |
| 793 |
and denial-of-service. |
| 794 |
<a href='https://sqlite.org/src/info/af4556bb5c285c08'>(details)</a></td> |
| 795 |
</tr> |
| 796 |
|
| 797 |
<tr><td valign='top'> |
| 798 |
<a id='CVE-2020-9327'></a> |
| 799 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2020-9327'>CVE-2020-9327</a> |
| 800 |
</td> |
| 801 |
<td valign='top'><a href="releaselog/3_32_0.html">3.32.0</a><br>(2020-05-22)</td> |
| 802 |
<td valign='top'>Malicious SQL statement causes a read using an uninitialized pointer |
| 803 |
and denial-of-service |
| 804 |
<a href='https://sqlite.org/src/info/4374860b29383380'>(details)</a></td> |
| 805 |
</tr> |
| 806 |
|
| 807 |
<tr><td valign='top'> |
| 808 |
<a id='CVE-2020-6405'></a> |
| 809 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2020-6405'>CVE-2020-6405</a> |
| 810 |
</td> |
| 811 |
<td valign='top'><a href="releaselog/3_31_0.html">3.31.0</a><br>(2020-01-22)</td> |
| 812 |
<td valign='top'>Malicious SQL statement causes a NULL pointer dereference and |
| 813 |
denial-of-service |
| 814 |
<a href='https://sqlite.org/src/info/1bc783da63d58b05'>(details)</a></td> |
| 815 |
</tr> |
| 816 |
|
| 817 |
<tr><td valign='top'> |
| 818 |
<a id='CVE-2019-20218'></a> |
| 819 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2019-20218'>CVE-2019-20218</a> |
| 820 |
</td> |
| 821 |
<td valign='top'><a href="releaselog/3_31_0.html">3.31.0</a><br>(2020-01-22)</td> |
| 822 |
<td valign='top'>Malicious SQL statement causes an uninitialized pointer read and |
| 823 |
denial-of-service. |
| 824 |
<a href='https://sqlite.org/src/timeline?r=better-error-handling-1'>(details)</a></td> |
| 825 |
</tr> |
| 826 |
|
| 827 |
<tr><td valign='top'> |
| 828 |
<a id='CVE-2019-19959'></a> |
| 829 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2019-19959'>CVE-2019-19959</a> |
| 830 |
</td> |
| 831 |
<td valign='top'><a href="releaselog/3_31_0.html">3.31.0</a><br>(2020-01-22)</td> |
| 832 |
<td valign='top'>Malicious SQL statement causes a NULL pointer dereference |
| 833 |
in the <a href="zipfile.html">Zipfile virtual table</a> extension and |
| 834 |
denial-of-service. This is only possible when the optional |
| 835 |
<a href="zipfile.html">Zipfile virtual table</a> extension is deployed, which is not |
| 836 |
the case in default builds. |
| 837 |
<a href='https://sqlite.org/src/info/cc0fb00a128fd077'>(details)</a></td> |
| 838 |
</tr> |
| 839 |
|
| 840 |
<tr><td valign='top'> |
| 841 |
<a id='CVE-2019-19926'></a> |
| 842 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2019-19926'>CVE-2019-19926</a> |
| 843 |
</td> |
| 844 |
<td valign='top'><a href="releaselog/3_31_0.html">3.31.0</a><br>(2020-01-22)</td> |
| 845 |
<td valign='top'>Malicious SQL statement causes an uninitialized pointer read and |
| 846 |
denial-of-service. |
| 847 |
<a href='https://sqlite.org/src/info/cba2a2a44cdf138a'>(details)</a></td> |
| 848 |
</tr> |
| 849 |
|
| 850 |
<tr><td valign='top'> |
| 851 |
<a id='CVE-2019-19925'></a> |
| 852 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2019-19925'>CVE-2019-19925</a> |
| 853 |
</td> |
| 854 |
<td valign='top'><a href="releaselog/3_31_0.html">3.31.0</a><br>(2020-01-22)</td> |
| 855 |
<td valign='top'>Malicious SQL statement causes a NULL pointer dereference and |
| 856 |
in the <a href="zipfile.html">Zipfile virtual table</a> extension and |
| 857 |
denial-of-service. This is only possible when the optional |
| 858 |
<a href="zipfile.html">Zipfile virtual table</a> extension is deployed, which is not |
| 859 |
the case in default builds. |
| 860 |
<a href='https://sqlite.org/src/info/a80f84b511231204'>(details)</a></td> |
| 861 |
</tr> |
| 862 |
|
| 863 |
<tr><td valign='top'> |
| 864 |
<a id='CVE-2019-19924'></a> |
| 865 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2019-19924'>CVE-2019-19924</a> |
| 866 |
</td> |
| 867 |
<td valign='top'><a href="releaselog/3_31_0.html">3.31.0</a><br>(2020-01-22)</td> |
| 868 |
<td valign='top'>Malicious SQL statement causes an uninitialized pointer reference and |
| 869 |
denial-of-service. |
| 870 |
<a href='https://sqlite.org/src/info/e2bddcd4c55ba3cb'>(details)</a></td> |
| 871 |
</tr> |
| 872 |
|
| 873 |
<tr><td valign='top'> |
| 874 |
<a id='CVE-2019-19923'></a> |
| 875 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2019-19923'>CVE-2019-19923</a> |
| 876 |
</td> |
| 877 |
<td valign='top'><a href="releaselog/3_31_0.html">3.31.0</a><br>(2020-01-22)</td> |
| 878 |
<td valign='top'>Malicious SQL statement causes a NULL pointer dereference and |
| 879 |
denial-of-service. |
| 880 |
<a href='https://sqlite.org/src/info/862974312edf00e9'>(details)</a></td> |
| 881 |
</tr> |
| 882 |
|
| 883 |
<tr><td valign='top'> |
| 884 |
<a id='CVE-2019-19646'></a> |
| 885 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2019-19646'>CVE-2019-19646</a> |
| 886 |
</td> |
| 887 |
<td valign='top'><a href="releaselog/3_31_0.html">3.31.0</a><br>(2020-01-22)</td> |
| 888 |
<td valign='top'>The <a href="pragma.html#pragma_integrity_check">PRAGMA integrity_check</a> command might cause the byte-code for a prepared |
| 889 |
statement to loop indefinitely. This might enable a denial-of-service, if the |
| 890 |
application has not taken appropriate and prudent steps |
| 891 |
to limit the run-time of SQL statements. This is not a vulnerability, as there |
| 892 |
are countless perfectly valid SQL queries, especially queries involving |
| 893 |
<a href="lang_with.html#recursivecte">recursive common table expressions</a>, that also run essentially forever. |
| 894 |
<a href='https://sqlite.org/src/info/bd8c280671ba44a7'>(details)</a></td> |
| 895 |
</tr> |
| 896 |
|
| 897 |
<tr><td valign='top'> |
| 898 |
<a id='CVE-2019-19317'></a> |
| 899 |
<a href='https://nvd.nist.gov/vuln/detail/CVE-2019-19317'>CVE-2019-19317</a> |
| 900 |
</td> |
| 901 |
<td valign='top'><a href="releaselog/3_31_0.html">3.31.0</a><br>(2020-01-22)</td> |
| 902 |
<td valign='top'>This CVE identifies a bug in a development check-in of |
| 903 |
SQLite. The bug never appeared in any official SQLite release. |
| 904 |
<a href='https://sqlite.org/src/info/6601da58032d18ae'>(details)</a></td> |
| 905 |
</tr> |
| 906 |
|
| 907 |
|
| 908 |
</tbody> |
| 909 |
</table> |
| 910 |
<p align="center"><small><i>This page was last updated on 2026-05-11 19:19:48Z </small></i></p> |
| 911 |
|