Skip to content

[SECURITY]: SQL Injection (CWE-89)

High
geekswamp published GHSA-cfwr-2m49-6gj3 Sep 29, 2024

Package

gomod https://github.com/arifai/zenith/blob/develop/internal/repository/notification.go (Go)

Affected versions

1.0.0

Patched versions

1.1.0

Description

Impact

The vulnerability is a SQL Injection (CWE-89). This allows an attacker to manipulate SQL queries by injecting arbitrary SQL commands through unsanitized input fields. Any system that processes database queries based on user input is potentially at risk. Attackers could exploit this vulnerability to view, modify, or delete sensitive data, or potentially execute administrative operations on the database.

Affected parties include:

  • Applications relying on user input for database operations.
  • Systems where input sanitization or parameterized queries are not properly implemented.

Patches

Current version

Workarounds

If upgrading is not possible, you can apply the following mitigations:

  • Ensure all database queries use parameterized queries or prepared statements.
  • Sanitize and validate all user inputs to avoid direct insertion into SQL queries.

References:

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
High
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H

CVE ID

CVE-2018-15133

Weaknesses

Credits