cve-2021-45346
Vulnerability from cvelistv5
Published
2022-02-14 00:00
Modified
2024-08-04 04:39
Severity ?
Summary
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.
References
cve@mitre.orghttps://github.com/guyinatuxedo/sqlite3_record_leakingExploit, Third Party Advisory
cve@mitre.orghttps://security.netapp.com/advisory/ntap-20220303-0001/Third Party Advisory
cve@mitre.orghttps://sqlite.org/forum/forumpost/056d557c2f8c452ed5Vendor Advisory
cve@mitre.orghttps://sqlite.org/forum/forumpost/53de8864ba114bf6Vendor Advisory
cve@mitre.orghttps://www.sqlite.org/cves.html#status_of_recent_sqlite_cvesVendor Advisory
af854a3a-2127-422b-91ae-364da2661108https://github.com/guyinatuxedo/sqlite3_record_leakingExploit, Third Party Advisory
af854a3a-2127-422b-91ae-364da2661108https://security.netapp.com/advisory/ntap-20220303-0001/Third Party Advisory
af854a3a-2127-422b-91ae-364da2661108https://sqlite.org/forum/forumpost/056d557c2f8c452ed5Vendor Advisory
af854a3a-2127-422b-91ae-364da2661108https://sqlite.org/forum/forumpost/53de8864ba114bf6Vendor Advisory
af854a3a-2127-422b-91ae-364da2661108https://www.sqlite.org/cves.html#status_of_recent_sqlite_cvesVendor Advisory
Impacted products
Vendor Product Version
Show details on NVD website

To clipboard 

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-04T04:39:20.536Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://github.com/guyinatuxedo/sqlite3_record_leaking"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://security.netapp.com/advisory/ntap-20220303-0001/"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://sqlite.org/forum/forumpost/53de8864ba114bf6"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://www.sqlite.org/cves.html#status_of_recent_sqlite_cves"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://sqlite.org/forum/forumpost/056d557c2f8c452ed5"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "n/a",
          "vendor": "n/a",
          "versions": [
            {
              "status": "affected",
              "version": "n/a"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "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."
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "description": "n/a",
              "lang": "en",
              "type": "text"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2022-10-31T00:00:00",
        "orgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
        "shortName": "mitre"
      },
      "references": [
        {
          "url": "https://github.com/guyinatuxedo/sqlite3_record_leaking"
        },
        {
          "url": "https://security.netapp.com/advisory/ntap-20220303-0001/"
        },
        {
          "url": "https://sqlite.org/forum/forumpost/53de8864ba114bf6"
        },
        {
          "url": "https://www.sqlite.org/cves.html#status_of_recent_sqlite_cves"
        },
        {
          "url": "https://sqlite.org/forum/forumpost/056d557c2f8c452ed5"
        }
      ],
      "tags": [
        "disputed"
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
    "assignerShortName": "mitre",
    "cveId": "CVE-2021-45346",
    "datePublished": "2022-02-14T00:00:00",
    "dateReserved": "2021-12-20T00:00:00",
    "dateUpdated": "2024-08-04T04:39:20.536Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2021-45346\",\"sourceIdentifier\":\"cve@mitre.org\",\"published\":\"2022-02-14T19:15:07.793\",\"lastModified\":\"2024-11-21T06:32:07.577\",\"vulnStatus\":\"Modified\",\"cveTags\":[{\"sourceIdentifier\":\"cve@mitre.org\",\"tags\":[\"disputed\"]}],\"descriptions\":[{\"lang\":\"en\",\"value\":\"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.\"},{\"lang\":\"es\",\"value\":\"** EN DISPUTA ** Se presenta una vulnerabilidad de p\u00e9rdida de memoria en SQLite Project SQLite3 versiones 3.35.1 y 3.37.0 por medio de consultas SQL dise\u00f1adas de forma maliciosa (realizadas por medio de la edici\u00f3n del archivo de la base de datos), es posible consultar un registro, y filtrar los bytes de memoria subsiguientes que son extendidos m\u00e1s all\u00e1 del registro, lo que podr\u00eda permitir a un usuario malicioso obtener informaci\u00f3n confidencial. NOTA: El desarrollador disputa esto como una vulnerabilidad afirmando que si le das a SQLite un archivo de base de datos corrupto y env\u00edas una consulta contra la base de datos, podr\u00eda leer partes de la base de datos que no pretend\u00edas o esperabas\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N\",\"baseScore\":4.3,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"LOW\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"NONE\"},\"exploitabilityScore\":2.8,\"impactScore\":1.4}],\"cvssMetricV2\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"2.0\",\"vectorString\":\"AV:N/AC:L/Au:S/C:P/I:N/A:N\",\"baseScore\":4.0,\"accessVector\":\"NETWORK\",\"accessComplexity\":\"LOW\",\"authentication\":\"SINGLE\",\"confidentialityImpact\":\"PARTIAL\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"NONE\"},\"baseSeverity\":\"MEDIUM\",\"exploitabilityScore\":8.0,\"impactScore\":2.9,\"acInsufInfo\":false,\"obtainAllPrivilege\":false,\"obtainUserPrivilege\":false,\"obtainOtherPrivilege\":false,\"userInteractionRequired\":false}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-401\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:sqlite:sqlite:3.35.1:*:*:*:*:*:*:*\",\"matchCriteriaId\":\"957B4E14-84C0-45C8-96C3-C78D17FB4DA5\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:sqlite:sqlite:3.37.0:*:*:*:*:*:*:*\",\"matchCriteriaId\":\"3CB2AF7E-0D10-47B6-B2F1-751A599A3E96\"}]}]},{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:netapp:ontap_select_deploy_administration_utility:-:*:*:*:*:*:*:*\",\"matchCriteriaId\":\"E7CF3019-975D-40BB-A8A4-894E62BD3797\"}]}]}],\"references\":[{\"url\":\"https://github.com/guyinatuxedo/sqlite3_record_leaking\",\"source\":\"cve@mitre.org\",\"tags\":[\"Exploit\",\"Third Party Advisory\"]},{\"url\":\"https://security.netapp.com/advisory/ntap-20220303-0001/\",\"source\":\"cve@mitre.org\",\"tags\":[\"Third Party Advisory\"]},{\"url\":\"https://sqlite.org/forum/forumpost/056d557c2f8c452ed5\",\"source\":\"cve@mitre.org\",\"tags\":[\"Vendor Advisory\"]},{\"url\":\"https://sqlite.org/forum/forumpost/53de8864ba114bf6\",\"source\":\"cve@mitre.org\",\"tags\":[\"Vendor Advisory\"]},{\"url\":\"https://www.sqlite.org/cves.html#status_of_recent_sqlite_cves\",\"source\":\"cve@mitre.org\",\"tags\":[\"Vendor Advisory\"]},{\"url\":\"https://github.com/guyinatuxedo/sqlite3_record_leaking\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Exploit\",\"Third Party Advisory\"]},{\"url\":\"https://security.netapp.com/advisory/ntap-20220303-0001/\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Third Party Advisory\"]},{\"url\":\"https://sqlite.org/forum/forumpost/056d557c2f8c452ed5\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Vendor Advisory\"]},{\"url\":\"https://sqlite.org/forum/forumpost/53de8864ba114bf6\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Vendor Advisory\"]},{\"url\":\"https://www.sqlite.org/cves.html#status_of_recent_sqlite_cves\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Vendor Advisory\"]}]}}"
  }
}


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 seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.