Skip to content

MindsDB can be made to not verify SSL certificates

Critical severity GitHub Reviewed Published Aug 1, 2023 in mindsdb/mindsdb • Updated Nov 10, 2023

Package

pip MindsDB (pip)

Affected versions

< 23.7.4.0

Patched versions

23.7.4.0

Description

Summary

MindsDB's AI Virtual Database allows developers to connect any AI/ML model to any datasource. Prior to version 23.7.4.0, a call to requests with verify=False disables SSL certificate checks. This rule enforces always verifying SSL certificates for methods in the Requests library. In version 23.7.4.0, certificates are validated by default, which is the desired behavior

Encryption in general is typically critical to the security of many applications. Using TLS can significantly increase security by guaranteeing the identity of the party you are communicating with. This is accomplished by one or both parties presenting trusted certificates during the connection initialization phase of TLS.

It is important to note that modules such as httplib within the Python standard library did not verify certificate chains until it was fixed in 2.7.9 release.

Details

Severity: Critical

References

@ZoranPandovski ZoranPandovski published to mindsdb/mindsdb Aug 1, 2023
Published to the GitHub Advisory Database Aug 1, 2023
Reviewed Aug 1, 2023
Published by the National Vulnerability Database Aug 4, 2023
Last updated Nov 10, 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
None

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:L/PR:N/UI:N/S:U/C:H/I:H/A:N

EPSS score

0.090%
(40th percentile)

Weaknesses

CVE ID

CVE-2023-38699

GHSA ID

GHSA-8hx6-qv6f-xgcw

Source code

Credits

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