gsd-2021-45346
Vulnerability from gsd
Modified
2023-12-13 01:23
Details
** DISPUTED ** 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.
Aliases
Aliases



{
   GSD: {
      alias: "CVE-2021-45346",
      description: "A Memory Leak vulnerabilty 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 malicous user obtain sensitive information..",
      id: "GSD-2021-45346",
      references: [
         "https://www.suse.com/security/cve/CVE-2021-45346.html",
      ],
   },
   gsd: {
      metadata: {
         exploitCode: "unknown",
         remediation: "unknown",
         reportConfidence: "confirmed",
         type: "vulnerability",
      },
      osvSchema: {
         aliases: [
            "CVE-2021-45346",
         ],
         details: "** DISPUTED ** 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: "GSD-2021-45346",
         modified: "2023-12-13T01:23:19.462129Z",
         schema_version: "1.4.0",
      },
   },
   namespaces: {
      "cve.org": {
         CVE_data_meta: {
            ASSIGNER: "cve@mitre.org",
            ID: "CVE-2021-45346",
            STATE: "PUBLIC",
         },
         affects: {
            vendor: {
               vendor_data: [
                  {
                     product: {
                        product_data: [
                           {
                              product_name: "n/a",
                              version: {
                                 version_data: [
                                    {
                                       version_value: "n/a",
                                    },
                                 ],
                              },
                           },
                        ],
                     },
                     vendor_name: "n/a",
                  },
               ],
            },
         },
         data_format: "MITRE",
         data_type: "CVE",
         data_version: "4.0",
         description: {
            description_data: [
               {
                  lang: "eng",
                  value: "** DISPUTED ** 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.",
               },
            ],
         },
         problemtype: {
            problemtype_data: [
               {
                  description: [
                     {
                        lang: "eng",
                        value: "n/a",
                     },
                  ],
               },
            ],
         },
         references: {
            reference_data: [
               {
                  name: "https://github.com/guyinatuxedo/sqlite3_record_leaking",
                  refsource: "MISC",
                  url: "https://github.com/guyinatuxedo/sqlite3_record_leaking",
               },
               {
                  name: "https://security.netapp.com/advisory/ntap-20220303-0001/",
                  refsource: "CONFIRM",
                  url: "https://security.netapp.com/advisory/ntap-20220303-0001/",
               },
               {
                  name: "https://sqlite.org/forum/forumpost/53de8864ba114bf6",
                  refsource: "MISC",
                  url: "https://sqlite.org/forum/forumpost/53de8864ba114bf6",
               },
               {
                  name: "https://www.sqlite.org/cves.html#status_of_recent_sqlite_cves",
                  refsource: "MISC",
                  url: "https://www.sqlite.org/cves.html#status_of_recent_sqlite_cves",
               },
               {
                  name: "https://sqlite.org/forum/forumpost/056d557c2f8c452ed5",
                  refsource: "MISC",
                  url: "https://sqlite.org/forum/forumpost/056d557c2f8c452ed5",
               },
            ],
         },
      },
      "nvd.nist.gov": {
         cve: {
            configurations: [
               {
                  nodes: [
                     {
                        cpeMatch: [
                           {
                              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",
                              vulnerable: true,
                           },
                        ],
                        negate: false,
                        operator: "OR",
                     },
                  ],
               },
               {
                  nodes: [
                     {
                        cpeMatch: [
                           {
                              criteria: "cpe:2.3:a:netapp:ontap_select_deploy_administration_utility:-:*:*:*:*:*:*:*",
                              matchCriteriaId: "E7CF3019-975D-40BB-A8A4-894E62BD3797",
                              vulnerable: true,
                           },
                        ],
                        negate: false,
                        operator: "OR",
                     },
                  ],
               },
            ],
            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érdida de memoria en SQLite Project SQLite3 versiones 3.35.1 y 3.37.0 por medio de consultas SQL diseñadas de forma maliciosa (realizadas por medio de la edición del archivo de la base de datos), es posible consultar un registro, y filtrar los bytes de memoria subsiguientes que son extendidos más allá del registro, lo que podría permitir a un usuario malicioso obtener información 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ías una consulta contra la base de datos, podría leer partes de la base de datos que no pretendías o esperabas",
               },
            ],
            id: "CVE-2021-45346",
            lastModified: "2024-04-11T01:13:23.817",
            metrics: {
               cvssMetricV2: [
                  {
                     acInsufInfo: false,
                     baseSeverity: "MEDIUM",
                     cvssData: {
                        accessComplexity: "LOW",
                        accessVector: "NETWORK",
                        authentication: "SINGLE",
                        availabilityImpact: "NONE",
                        baseScore: 4,
                        confidentialityImpact: "PARTIAL",
                        integrityImpact: "NONE",
                        vectorString: "AV:N/AC:L/Au:S/C:P/I:N/A:N",
                        version: "2.0",
                     },
                     exploitabilityScore: 8,
                     impactScore: 2.9,
                     obtainAllPrivilege: false,
                     obtainOtherPrivilege: false,
                     obtainUserPrivilege: false,
                     source: "nvd@nist.gov",
                     type: "Primary",
                     userInteractionRequired: false,
                  },
               ],
               cvssMetricV31: [
                  {
                     cvssData: {
                        attackComplexity: "LOW",
                        attackVector: "NETWORK",
                        availabilityImpact: "NONE",
                        baseScore: 4.3,
                        baseSeverity: "MEDIUM",
                        confidentialityImpact: "LOW",
                        integrityImpact: "NONE",
                        privilegesRequired: "LOW",
                        scope: "UNCHANGED",
                        userInteraction: "NONE",
                        vectorString: "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
                        version: "3.1",
                     },
                     exploitabilityScore: 2.8,
                     impactScore: 1.4,
                     source: "nvd@nist.gov",
                     type: "Primary",
                  },
               ],
            },
            published: "2022-02-14T19:15:07.793",
            references: [
               {
                  source: "cve@mitre.org",
                  tags: [
                     "Exploit",
                     "Third Party Advisory",
                  ],
                  url: "https://github.com/guyinatuxedo/sqlite3_record_leaking",
               },
               {
                  source: "cve@mitre.org",
                  tags: [
                     "Third Party Advisory",
                  ],
                  url: "https://security.netapp.com/advisory/ntap-20220303-0001/",
               },
               {
                  source: "cve@mitre.org",
                  tags: [
                     "Vendor 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",
               },
            ],
            sourceIdentifier: "cve@mitre.org",
            vulnStatus: "Modified",
            weaknesses: [
               {
                  description: [
                     {
                        lang: "en",
                        value: "CWE-401",
                     },
                  ],
                  source: "nvd@nist.gov",
                  type: "Primary",
               },
            ],
         },
      },
   },
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.