opensearch-project/performance-analyzer-rca

sqlite-jdbc-3.32.3.2.jar: 1 vulnerabilities (highest severity is: 8.8) - autoclosed

mend-for-github-com opened this issue · 1 comments

Vulnerable Library - sqlite-jdbc-3.32.3.2.jar

SQLite JDBC library

Path to dependency file: /build.gradle

Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.xerial/sqlite-jdbc/3.32.3.2/ee9912c1bdec16fe5978b0abd9f4063ce9eedf8b/sqlite-jdbc-3.32.3.2.jar

Found in HEAD commit: 9d100f9766d2613ccbb9be07cbdf467332a22eea

Vulnerabilities

CVE Severity CVSS Dependency Type Fixed in (sqlite-jdbc version) Remediation Available
CVE-2023-32697 High 8.8 sqlite-jdbc-3.32.3.2.jar Direct 3.41.2.2

Details

CVE-2023-32697

Vulnerable Library - sqlite-jdbc-3.32.3.2.jar

SQLite JDBC library

Path to dependency file: /build.gradle

Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.xerial/sqlite-jdbc/3.32.3.2/ee9912c1bdec16fe5978b0abd9f4063ce9eedf8b/sqlite-jdbc-3.32.3.2.jar

Dependency Hierarchy:

  • sqlite-jdbc-3.32.3.2.jar (Vulnerable Library)

Found in HEAD commit: 9d100f9766d2613ccbb9be07cbdf467332a22eea

Found in base branch: main

Vulnerability Details

SQLite JDBC is a library for accessing and creating SQLite database files in Java. Sqlite-jdbc addresses a remote code execution vulnerability via JDBC URL. This issue impacting versions 3.6.14.1 through 3.41.2.1 and has been fixed in version 3.41.2.2.

Publish Date: 2023-05-23

URL: CVE-2023-32697

CVSS 3 Score Details (8.8)

Base Score Metrics:

  • Exploitability Metrics:
    • Attack Vector: Network
    • Attack Complexity: Low
    • Privileges Required: Low
    • User Interaction: None
    • Scope: Unchanged
  • Impact Metrics:
    • Confidentiality Impact: High
    • Integrity Impact: High
    • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-6phf-6h5g-97j2

Release Date: 2023-05-23

Fix Resolution: 3.41.2.2

⛑️ Automatic Remediation is available for this issue


⛑️ Automatic Remediation is available for this issue.

✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.