Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Merge fixes from the 3.32 branch. |
|---|---|
| Downloads: | Tarball | ZIP archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
e3d95c44b7fbb149dd76b8ce560491ba |
| User & Date: | drh 2020-06-29 11:40:23.436 |
Context
|
2020-07-09
| ||
| 15:12 | Fix minor typo in the transaction documentation. (check-in: fd1f6c62f7 user: drh tags: trunk) | |
|
2020-06-29
| ||
| 11:40 | Merge fixes from the 3.32 branch. (check-in: e3d95c44b7 user: drh tags: trunk) | |
| 01:26 | Update the CVE list. (check-in: 7565236dfd user: drh tags: branch-3.32) | |
|
2020-06-28
| ||
| 16:36 | Correction to how Knuth names B-Tree algorithm variants in the file format document. (check-in: ea334221a0 user: drh tags: trunk) | |
Changes
Changes to pages/cves.in.
| ︙ | ︙ | |||
258 259 260 261 262 263 264 265 266 267 268 269 270 271 |
<th valign="bottom">Fix</th>
<th valign="bottom">Comments</th>
</tr>
</thead>
<tbody>
<tcl>
CVE 2020-13871 3.32.3 {
Malicious SQL statement causes a read-only use-after-free memory error.
} {https://sqlite.org/src/info/c8d3b9f0a750a529}
CVE 2020-13632 3.32.0 {
Malicious SQL statement causes a read of a NULL pointer in the
[matchinfo()] SQL function of the [FTS3] extension, resulting in
| > > > > | 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 |
<th valign="bottom">Fix</th>
<th valign="bottom">Comments</th>
</tr>
</thead>
<tbody>
<tcl>
CVE 2020-15358 3.32.3 {
Malicious SQL statement causes an read past the end of a heap buffer.
} {https://sqlite.org/src/info/8f157e8010b22af0}
CVE 2020-13871 3.32.3 {
Malicious SQL statement causes a read-only use-after-free memory error.
} {https://sqlite.org/src/info/c8d3b9f0a750a529}
CVE 2020-13632 3.32.0 {
Malicious SQL statement causes a read of a NULL pointer in the
[matchinfo()] SQL function of the [FTS3] extension, resulting in
|
| ︙ | ︙ |
Changes to pages/lang_altertable.in.
| ︙ | ︙ | |||
318 319 320 321 322 323 324 | enhancements to the internal schema representation. Changing the internal schema representation would be much more difficult if the schema representation was exposed in the database file. So, in other words, storing the schema as text helps maintain backwards compatibility, and helps ensure that older database files can be read and written by newer versions of SQLite. | | | 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 | enhancements to the internal schema representation. Changing the internal schema representation would be much more difficult if the schema representation was exposed in the database file. So, in other words, storing the schema as text helps maintain backwards compatibility, and helps ensure that older database files can be read and written by newer versions of SQLite. <p>Storing the schema as text also makes the [SQLite database file format] easier to define, document, and understand. This helps make SQLite database files a [recommended storage format] for long-term archiving of data. <p>The downside of storing schema a text is that it can make the schema tricky to modify. And for that reason, the ALTER TABLE support in SQLite has traditionally lagged behind other SQL |
| ︙ | ︙ |