CyberSecBulletin
CVE-2023-7104NVD status: Modified

SQLite3: Improper Restriction of Operations within the Bounds of a Memory Buffer

Published Updated By the CyberSecBulletin desk

CVE-2023-7104 is a high-severity improper restriction of operations within the bounds of a memory buffer vulnerability in SQLite3 from SQLite, with a CVSS 3.1 base score of 7.3 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected SQLite3 versions: 3.0; 3.1; 3.2, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.46% chance of exploitation within 30 days, higher than 74% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update RUGGEDCOM CROSSBOW Station Access Controller (SAC) to V5.6 or a later version.
  2. Update SIDIS Prime to V4.0.700 or a later version.
  3. Update SIMATIC S7-1500 TM MFP - GNU/Linux subsystem to V1.1 or a later version.
  4. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
SQLiteSQLite33.0; 3.1; 3.2; 3.3; 3.4; 3.5; 3.6; 3.7; and 32 more rangesNot stated
SiemensRUGGEDCOM CROSSBOW Station Access Controller (SAC)before V5.6V5.6
SiemensSIDIS Primebefore V4.0.700V4.0.700
SiemensSIMATIC S7-1500 TM MFP - GNU/Linux subsystembefore V1.1V1.1
SqliteSqlite3.43.0 and earlierNot stated
Fedora ProjectFedora38; 39Not stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
LowSome restricted data can be read.
Integrity
LowLimited modification of data is possible.
Availability
LowPerformance or availability is reduced.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.15.5MediumCNA (vuldb.com)
CVSS 3.17.3HighNVD
CVSS 2.05.2MediumCNA (vuldb.com)

Official description

A vulnerability was found in SQLite SQLite3 up to 3.43.0 and classified as critical. This issue affects the function sessionReadRecord of the file ext/session/sqlite3session.c of the component make alltest Handler. The manipulation leads to heap-based buffer overflow. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-248999.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Restriction of Operations within the Bounds of a Memory Buffer

The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary.

How developers prevent this class of flaw

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.

More Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerabilities (CWE-119)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Patches and release notes

Technical write-ups (may include proof of concept)

Recent Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerabilities

Spotted an error? Tell us.