{"vulnerability": "CVE-2021-2023", "sightings": [{"uuid": "9f92512c-0522-4b1f-b28e-66bba13b0ea2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2021-20238", "type": "seen", "source": "https://t.me/cibsecurity/40054", "content": "\u203c CVE-2021-20238 \u203c\n\nIt was found in OpenShift Container Platform 4 that ignition config, served by the Machine Config Server, can be accessed externally from clusters without authentication. The MCS endpoint (port 22623) provides ignition configuration used for bootstrapping Nodes and can include some sensitive data, e.g. registry pull secrets. There are two scenarios where this data can be accessed. The first is on Baremetal, OpenStack, Ovirt, Vsphere and KubeVirt deployments which do not have a separate internal API endpoint and allow access from outside the cluster to port 22623 from the standard OpenShift API Virtual IP address. The second is on cloud deployments when using unsupported network plugins, which do not create iptables rules that prevent to port 22623. In this scenario, the ignition config is exposed to all pods within the cluster and cannot be accessed externally.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-04-02T02:26:15.000000Z"}, {"uuid": "877d0880-add3-4db2-8dbb-c95d33449c21", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2021-20232", "type": "seen", "source": "https://t.me/cibsecurity/24871", "content": "\u203c CVE-2021-20232 \u203c\n\nA flaw was found in gnutls. A use after free issue in client_send_params in lib/ext/pre_shared_key.c may lead to memory corruption and other potential consequences.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2021-03-12T22:57:36.000000Z"}, {"uuid": "6d6b876e-8493-4b9a-9e83-3601da84ea7c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2021-20239", "type": "published-proof-of-concept", "source": "https://t.me/BABATATASASA/5977", "content": "|       CVE-2021-3569   2.1     https://vulners.com/cve/CVE-2021-3569\n|       CVE-2021-3527   2.1     https://vulners.com/cve/CVE-2021-3527                               |       CVE-2021-3446   2.1     https://vulners.com/cve/CVE-2021-3446                               |       CVE-2021-3416   2.1     https://vulners.com/cve/CVE-2021-3416                               |       CVE-2021-20320  2.1     https://vulners.com/cve/CVE-2021-20320\n|       CVE-2021-20297  2.1     https://vulners.com/cve/CVE-2021-20297                              |       CVE-2021-20257  2.1     https://vulners.com/cve/CVE-2021-20257                              |       CVE-2021-20239  2.1     https://vulners.com/cve/CVE-2021-20239                              |       CVE-2021-20221  2.1     https://vulners.com/cve/CVE-2021-20221\n|       CVE-2020-25743  2.1     https://vulners.com/cve/CVE-2020-25743\n|       CVE-2020-12458  2.1     https://vulners.com/cve/CVE-2020-12458\n|       CVE-2020-10756  2.1     https://vulners.com/cve/CVE-2020-10756\n|       CVE-2019-18391  2.1     https://vulners.com/cve/CVE-2019-18391\n|       CVE-2019-14826  2.1     https://vulners.com/cve/CVE-2019-14826\n|       CVE-2019-13313  2.1     https://vulners.com/cve/CVE-2019-13313                              |       CVE-2019-12067  2.1     https://vulners.com/cve/CVE-2019-12067                              |       CVE-2019-11884  2.1     https://vulners.com/cve/CVE-2019-11884                              |       CVE-2019-11833  2.1     https://vulners.com/cve/CVE-2019-11833                              |       CVE-2019-11135  2.1     https://vulners.com/cve/CVE-2019-11135                              |       CVE-2019-10183  2.1     https://vulners.com/cve/CVE-2019-10183                              |       CVE-2018-16878  2.1     https://vulners.com/cve/CVE-2018-16878                              |       CVE-2004-0554   2.1     https://vulners.com/cve/CVE-2004-0554                               |       1AC912AC-B7DA-5F88-B22A-12B17E5D1D5C    2.1       https://vulners.com/githubexploit/1AC912AC-B7DA-5F88-B22A-12B17E5D1D5C    *EXPLOIT*\n|       CVE-2023-1289   1.9     https://vulners.com/cve/CVE-2023-1289\n|       CVE-2022-25310  1.9     https://vulners.com/cve/CVE-2022-25310                              |       CVE-2022-25309  1.9     https://vulners.com/cve/CVE-2022-25309                              |       CVE-2021-4217   1.9     https://vulners.com/cve/CVE-2021-4217                               |       CVE-2021-3753   1.9     https://vulners.com/cve/CVE-2021-3753                               |       CVE-2021-3602   1.9     https://vulners.com/cve/CVE-2021-3602                               |       CVE-2020-25656  1.9     https://vulners.com/cve/CVE-2020-25656                              |       CVE-2019-2634   1.9     https://vulners.com/cve/CVE-2019-2634                               |       CVE-2019-2535   1.9     https://vulners.com/cve/CVE-2019-2535                               |       CVE-2019-18660  1.9     https://vulners.com/cve/CVE-2019-18660\n|       PRION:CVE-2023-22024    1.7     https://vulners.com/prion/PRION:CVE-2023-22024\n|       CVE-2023-3161   1.7     https://vulners.com/cve/CVE-2023-3161\n|       CVE-2023-28328  1.7     https://vulners.com/cve/CVE-2023-28328\n|       CVE-2023-28327  1.7     https://vulners.com/cve/CVE-2023-28327\n|       CVE-2023-2700   1.7     https://vulners.com/cve/CVE-2023-2700\n|       CVE-2023-2602   1.7     https://vulners.com/cve/CVE-2023-2602\n|       CVE-2023-1981   1.7     https://vulners.com/cve/CVE-2023-1981\n|       CVE-2023-1095   1.7     https://vulners.com/cve/CVE-2023-1095                               |       CVE-2022-2153   1.7     https://vulners.com/cve/CVE-2022-2153\n|       CVE-2022-1263   1.7     https://vulners.com/cve/CVE-2022-1263", "creation_timestamp": "2023-11-15T16:53:03.000000Z"}, {"uuid": "58fcc232-002a-4402-9d75-7c9fdd7d8dc7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2021-20231", "type": "seen", "source": "https://t.me/cibsecurity/24861", "content": "\u203c CVE-2021-20231 \u203c\n\nA flaw was found in gnutls. A use after free issue in client sending key_share extension may lead to memory corruption and other consequences.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2021-03-12T22:57:22.000000Z"}, {"uuid": "fbe3f7fc-ee67-4f46-9b10-82a5699cf112", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2021-20230", "type": "seen", "source": "https://t.me/cibsecurity/24015", "content": "\u203c CVE-2021-20230 \u203c\n\nA flaw was found in stunnel before 5.57, where it improperly validates client certificates when it is configured to use both redirect and verifyChain options. This flaw allows an attacker with a certificate signed by a Certificate Authority, which is not the one accepted by the stunnel server, to access the tunneled service instead of being redirected to the address specified in the redirect option. The highest threat from this vulnerability is to confidentiality.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2021-02-23T20:35:31.000000Z"}, {"uuid": "cb69f75f-6c18-4272-b1c3-5ab462fbff6e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2021-2023", "type": "seen", "source": "https://t.me/cibsecurity/22403", "content": "\u203c CVE-2021-2023 \u203c\n\nVulnerability in the Oracle Installed Base product of Oracle E-Business Suite (component: APIs). Supported versions that are affected are 12.1.1-12.1.3 and 12.2.3-12.2.9. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Installed Base. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Installed Base, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Installed Base accessible data. CVSS 3.1 Base Score 4.7 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N).\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2021-01-20T18:40:36.000000Z"}]}