{"uuid": "c8ce4df3-53e3-4d73-8d70-fefd84caa4eb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-35737", "type": "seen", "source": "https://t.me/hacking_Attack/74938", "content": "Black Hat Ethical Hacking\nSQLite patches 22-year-old code execution, a DoS vulnerability\n\nSQLite patches 22-year-old code execution, a DoS vulnerabilityPost Views: 1 Premium Contenthttps://www.blackhatethicalhacking.com/wp-content/uploads/2022/09/Patreon.png Subscribe to Patreon to watch this episode.\nReading Time: 3 Minutes The maintainers of the SQLite database engine have patched a high severity\u00a0vulnerability (DoS)\u00a0that attackers could exploit to crash or control programs that rely on the software.Developers of the software have offered The Daily Swig\u00a0a convincing argument that the flaw would be difficult to exploit in practice. Even so, they have revised the software with a patch to defend against the flaw \u2013 rather than dismissing the issue as something that can be safely ignored. SQLite\u00a0is a popular open source C-language library that underpins many enterprise apps and services. Notable users of SQLite\u00a0include Apple, Adobe, Google, Facebook, and Microsoft. There are billions of copies of SQLite deployed worldwide.\n\nThe SQLite team is quick to fix emerging vulnerabilities in the software due to their potentially wide-reaching impact. However, a vulnerability disclosed this month by Trail of Bits was introduced 22 years ago and highlighted how initially secure functionality could have unintended consequences much further down the line.\n\nIn a blog post\u00a0dated October 25, Trail of Bits researcher Andreas Kellas said the vulnerability was introduced in SQLite version 1.0.12, a 2000 release that landed when the software was primarily based on 32-bit architectures. According to Kellas, the bug \u201cmay not have seemed like an error\u201d at the time.\n\nThe high severity vulnerability is tracked as CVE-2022-35737, scoring a CVSS severity score of 7.5.\n\nTrail of Bits said the bug impacts any app that relies on the SQLite library API.\n\nThe vulnerability is exploitable on 64-bit systems when large string inputs contain %Q, %q, or %w\u00a0format substitution types that \u2013 in this scenario \u2013 might cause programs to crash or worse.\n\nIn the most severe cases \u2013 when the !\u00a0special character exists in the format string \u2013 it may be \u201cpossible to achieve arbitrary code execution, in the worst case, or to cause the program to hang and loop (nearly) indefinitely,\u201d according to the researchers.\nSee Also: So you want to be a hacker? Complete Offensive Security and Ethical Hacking Course Root cause analysisSpeaking to The Daily Swig, the creator of SQLite, D. Richard Hipp, said the root cause of the problem was the use of signed 32-bit integers as a byte index into the input string and to compute the size of the output string. When an input string was large enough, the integer would overflow, and \u201call kinds of problems\u201d ensued.\n\nHowever, the potential impact of the flaw appears to be limited.\n\nHipp told us that it is not possible to reach the vulnerability for malicious purposes via SQL inputs or by passing SQLite a malformed database file. Instead, an attacker would have to abuse the use the sqlite3_mprintf()\u00a0function \u2013 or \u201csimilar C-level interfaces with a format string that includes one of the non-standard [;\u2026]\u00a0conversion symbols, and then pass in a string that is over 2GB in size\u201d.\n\nThe software developer added:\n\n\u201cLots of applications use SQLite, but only a small percentage of those use the sqlite3_mprintf() API, and an even smaller percentage make use of %Q, %q, or %w. Of those that do, most do not provide a way for an attacker to arrange for a 2GB+ string to be passed into the argument to %Q, %q, or %w.\u201d\nTrending: Exploit XSS Injections in a one-line powerful Technique\nTrending: Recon Tool: Hakrawler Unearthing FossilIn addition, while the project uses the Fossil control system and this software uses printf, the team [...]\n\n___________________________ \n@hacking_Attack\n@Hacking_Video", "creation_timestamp": "2026-09-06T00:00:57.512691Z"}