TLS disabled by default in select aws/sagemaker-python-sdk configurations
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| AWS | SageMaker Python SDK | unaffected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Amazon | Sagemaker Python Sdk | — |
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-62rc-f4v9-h543 | SageMaker Python SDK has Insecure TLS Configuration |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.260% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Amazon
Amazon sagemaker Python Sdk |
|
| Vendors & Products |
Amazon
Amazon sagemaker Python Sdk |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Amazon SageMaker Python SDK before v3.1.1 or v2.256.0 disables TLS certificate verification for HTTPS connections made by the service when a Triton Python model is imported, incorrectly allowing for requests with invalid and self-signed certificates to succeed. | |
| Title | TLS disabled by default in select aws/sagemaker-python-sdk configurations | |
| Weaknesses | CWE-295 | |
| References |
| |
| Metrics |
cvssV3_1
|