Skip to content

mysql-bunuuid-rails vulnerable to SQL injection

Critical severity GitHub Reviewed Published Oct 30, 2018 to the GitHub Advisory Database • Updated Aug 25, 2023

Package

bundler mysql-binuuid-rails (RubyGems)

Affected versions

< 1.1.1

Patched versions

1.1.1

Description

mysql-binuuid-rails 1.1.0 and earlier allows SQL Injection because it removes default string escaping for affected database columns.

References

Published to the GitHub Advisory Database Oct 30, 2018
Reviewed Jun 16, 2020
Last updated Aug 25, 2023

Severity

Critical

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
Low
Privileges required
None
User interaction
None
Scope
Unchanged
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.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.226%
(61st percentile)

Weaknesses

CVE ID

CVE-2018-18476

GHSA ID

GHSA-6j63-35hj-vmcg

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.