Vulnerability from bitnami_vulndb
Published
2024-03-06 11:06
Modified
2025-04-03 14:40
Summary
Details

A Memory Leak vulnerability exists in SQLite Project SQLite3 3.35.1 and 3.37.0 via maliciously crafted SQL Queries (made via editing the Database File), it is possible to query a record, and leak subsequent bytes of memory that extend beyond the record, which could let a malicious user obtain sensitive information. NOTE: The developer disputes this as a vulnerability stating that If you give SQLite a corrupted database file and submit a query against the database, it might read parts of the database that you did not intend or expect.

To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "Bitnami",
        "name": "sqlite",
        "purl": "pkg:bitnami/sqlite"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "3.35.1"
            },
            {
              "fixed": "3.35.2"
            },
            {
              "introduced": "3.37.0"
            },
            {
              "fixed": "3.37.1"
            }
          ],
          "type": "SEMVER"
        }
      ],
      "severity": [
        {
          "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
          "type": "CVSS_V3"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2021-45346"
  ],
  "database_specific": {
    "cpes": [
      "cpe:2.3:a:sqlite:sqlite:3.35.1:*:*:*:*:*:*:*",
      "cpe:2.3:a:sqlite:sqlite:3.37.0:*:*:*:*:*:*:*",
      "cpe:2.3:a:sqlite:sqlite:*:*:*:*:*:*:*:*"
    ],
    "severity": "Medium"
  },
  "details": "A Memory Leak vulnerability exists in SQLite Project SQLite3 3.35.1 and 3.37.0 via maliciously crafted SQL Queries (made via editing the Database File), it is possible to query a record, and leak subsequent bytes of memory that extend beyond the record, which could let a malicious user obtain sensitive information. NOTE: The developer disputes this as a vulnerability stating that If you give SQLite a corrupted database file and submit a query against the database, it might read parts of the database that you did not intend or expect.",
  "id": "BIT-sqlite-2021-45346",
  "modified": "2025-04-03T14:40:37.652Z",
  "published": "2024-03-06T11:06:14.888Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/guyinatuxedo/sqlite3_record_leaking"
    },
    {
      "type": "WEB",
      "url": "https://security.netapp.com/advisory/ntap-20220303-0001/"
    },
    {
      "type": "WEB",
      "url": "https://sqlite.org/forum/forumpost/056d557c2f8c452ed5"
    },
    {
      "type": "WEB",
      "url": "https://sqlite.org/forum/forumpost/53de8864ba114bf6"
    },
    {
      "type": "WEB",
      "url": "https://www.sqlite.org/cves.html#status_of_recent_sqlite_cves"
    },
    {
      "type": "WEB",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2021-45346"
    }
  ],
  "schema_version": "1.5.0"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.