Ceph is a distributed object, block, and file storage platform. This repo is a fork of that repo that the CORTX community uses to stage our changes for the purposes of creating and maintaining a motr SAL backend for RGW.
Path to dependency file: /src/pybind/mgr/requirements.txt
Path to vulnerable library: /src/pybind/mgr/requirements.txt,/src/ceph-volume,/src/pybind/rgw,/src/tools/cephfs/top,/src/pybind/rados,/src/pybind/mgr/dashboard/requirements.txt,/src/pybind/cephfs,/admin/doc-requirements.txt,/src/pybind/rbd,/src/pybind/mgr/requirements.txt,/src/tools/cephfs/shell
There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING. When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.
CVE-2023-0286 - High Severity Vulnerability
cryptography is a package which provides cryptographic recipes and primitives to Python developers.
Library home page: https://files.pythonhosted.org/packages/37/19/234484df6fc7bdf4cf81cd4a89f600fce9f8f7a4bc1b307d7abbcd382b64/cryptography-38.0.3-cp36-abi3-manylinux_2_24_x86_64.whl
Path to dependency file: /src/pybind/mgr/requirements.txt
Path to vulnerable library: /src/pybind/mgr/requirements.txt,/src/ceph-volume,/src/pybind/rgw,/src/tools/cephfs/top,/src/pybind/rados,/src/pybind/mgr/dashboard/requirements.txt,/src/pybind/cephfs,/admin/doc-requirements.txt,/src/pybind/rbd,/src/pybind/mgr/requirements.txt,/src/tools/cephfs/shell
Dependency Hierarchy: - :x: **cryptography-38.0.3-cp36-abi3-manylinux_2_24_x86_64.whl** (Vulnerable Library)
Found in HEAD commit: b7c0ec1e6a9bc4b3d908a672c3a8228bdb8dfbd0
Found in base branch: main
There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING. When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.
Publish Date: 2023-02-08
URL: CVE-2023-0286
Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: None - Availability Impact: High
For more information on CVSS3 Scores, click here.Type: Upgrade version
Origin: https://github.com/advisories/GHSA-x4qr-2fvf-3mr5
Release Date: 2023-02-08
Fix Resolution: OpenSSL_1_0_2a--OpenSSL_1_0_2u;OpenSSL_1_1_1a--OpenSSL_1_1_1s;cryptography - 39.0.1
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.