summaryrefslogtreecommitdiffstats
path: root/www/cves.html
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2024-09-19 04:07:41 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2024-09-19 04:07:41 +0000
commit2abec11ad14687c1c717bb9c570e78525c84ee0f (patch)
treed15af7ac53ab21adc710992e03486cf99ddb626f /www/cves.html
parentAdding debian version 3.46.0-1. (diff)
downloadsqlite3-2abec11ad14687c1c717bb9c570e78525c84ee0f.tar.xz
sqlite3-2abec11ad14687c1c717bb9c570e78525c84ee0f.zip
Merging upstream version 3.46.1.
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'www/cves.html')
-rw-r--r--www/cves.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/www/cves.html b/www/cves.html
index 75b22da..c87bf42 100644
--- a/www/cves.html
+++ b/www/cves.html
@@ -235,7 +235,7 @@ behind CVEs is sound. They provide a common naming scheme whereby
software bugs that might compromise information security can be easily
tracked.
-</p><p>While the original idea being CVEs is sound, the current processes for
+</p><p>While the original idea behind CVEs is sound, the current processes for
creating and managing CVEs are inadequate. There are countless grey-hat
hackers running fuzzers against a wide-variety of open-source software
products (SQLite as well as many others) and writing up CVEs against
@@ -779,5 +779,5 @@ be added.
</tbody>
</table>
-
+<p align="center"><small><i>This page last modified on <a href="https://sqlite.org/docsrc/honeypot" id="mtimelink" data-href="https://sqlite.org/docsrc/finfo/pages/cves.in?m=376423da67">2024-07-02 11:43:42</a> UTC </small></i></p>