{"vulnerability": "CVE-2022-2132", "sightings": [{"uuid": "ac6adac1-244a-40e9-949a-fd93bcc3b9dd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-21321", "type": "published-proof-of-concept", "source": "https://t.me/BABATATASASA/5994", "content": "| PRION:CVE-2022-21605 3.3 https://vulners.com/prion/PRION:CVE-2022-21605 | PRION:CVE-2022-21604 3.3 https://vulners.com/prion/PRION:CVE-2022-21604 | PRION:CVE-2022-21599 3.3 https://vulners.com/prion/PRION:CVE-2022-21599 | PRION:CVE-2022-21594 3.3 https://vulners.com/prion/PRION:CVE-2022-21594 | PRION:CVE-2021-2307 3.3 https://vulners.com/prion/PRION:CVE-2021-2307\n| PRION:CVE-2023-21875 3.2 https://vulners.com/prion/PRION:CVE-2023-21875\n| PRION:CVE-2022-39403 3.0 https://vulners.com/prion/PRION:CVE-2022-39403\n| PRION:CVE-2022-21486 2.9 https://vulners.com/prion/PRION:CVE-2022-21486\n| PRION:CVE-2022-21485 2.9 https://vulners.com/prion/PRION:CVE-2022-21485 | PRION:CVE-2022-21484 2.9 https://vulners.com/prion/PRION:CVE-2022-21484\n| PRION:CVE-2022-21357 2.9 https://vulners.com/prion/PRION:CVE-2022-21357\n| PRION:CVE-2022-21355 2.9 https://vulners.com/prion/PRION:CVE-2022-21355 | PRION:CVE-2022-21333 2.9 https://vulners.com/prion/PRION:CVE-2022-21333 | PRION:CVE-2022-21331 2.9 https://vulners.com/prion/PRION:CVE-2022-21331\n| PRION:CVE-2022-21325 2.9 https://vulners.com/prion/PRION:CVE-2022-21325\n| PRION:CVE-2022-21324 2.9 https://vulners.com/prion/PRION:CVE-2022-21324\n| PRION:CVE-2022-21323 2.9 https://vulners.com/prion/PRION:CVE-2022-21323\n| PRION:CVE-2022-21321 2.9 https://vulners.com/prion/PRION:CVE-2022-21321 | PRION:CVE-2022-21319 2.9 https://vulners.com/prion/PRION:CVE-2022-21319\n| PRION:CVE-2022-21317 2.9 https://vulners.com/prion/PRION:CVE-2022-21317\n| PRION:CVE-2022-21313 2.9 https://vulners.com/prion/PRION:CVE-2022-21313 | PRION:CVE-2022-21312 2.9 https://vulners.com/prion/PRION:CVE-2022-21312 | PRION:CVE-2022-21311 2.9 https://vulners.com/prion/PRION:CVE-2022-21311\n| PRION:CVE-2019-2797 2.3 https://vulners.com/prion/PRION:CVE-2019-2797\n| PRION:CVE-2022-39402 2.1 https://vulners.com/prion/PRION:CVE-2022-39402\n| PRION:CVE-2022-21460 2.1 https://vulners.com/prion/PRION:CVE-2022-21460\n| PRION:CVE-2022-21451 2.1 https://vulners.com/prion/PRION:CVE-2022-21451 | PRION:CVE-2022-21444 2.1 https://vulners.com/prion/PRION:CVE-2022-21444\n| PRION:CVE-2021-35632 2.1 https://vulners.com/prion/PRION:CVE-2021-35632\n| PRION:CVE-2021-2042 2.1 https://vulners.com/prion/PRION:CVE-2021-2042 | PRION:CVE-2019-2969 2.1 https://vulners.com/prion/PRION:CVE-2019-2969 | PRION:CVE-2021-2232 1.9 https://vulners.com/prion/PRION:CVE-2021-2232\n| PRION:CVE-2019-2634 1.9 https://vulners.com/prion/PRION:CVE-2019-2634\n| PRION:CVE-2019-2535 1.9 https://vulners.com/prion/PRION:CVE-2019-2535\n| PRION:CVE-2018-3174 1.9 https://vulners.com/prion/PRION:CVE-2018-3174\n| PRION:CVE-2018-3084 1.9 https://vulners.com/prion/PRION:CVE-2018-3084\n| PRION:CVE-2023-22058 1.7 https://vulners.com/prion/PRION:CVE-2023-22058\n| PRION:CVE-2022-21625 1.7 https://vulners.com/prion/PRION:CVE-2022-21625\n| PRION:CVE-2022-21595 1.7 https://vulners.com/prion/PRION:CVE-2022-21595 | PRION:CVE-2019-2536 1.2 https://vulners.com/prion/PRION:CVE-2019-2536\n| PRION:CVE-2019-2513 1.2 https://vulners.com/prion/PRION:CVE-2019-2513\n|_ PRION:CVE-2022-21611 0.8 https://vulners.com/prion/PRION:CVE-2022-21611 8443/tcp closed https-alt conn-refused 30000/tcp closed ndmps conn-refused 30718/tcp closed unknown conn-refused 30951/tcp closed unknown conn-refused", "creation_timestamp": "2023-11-15T17:01:59.000000Z"}, {"uuid": "7f02fb47-05ca-4d16-b070-2f61d2133702", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-21324", "type": "published-proof-of-concept", "source": "https://t.me/BABATATASASA/5994", "content": "| PRION:CVE-2022-21605 3.3 https://vulners.com/prion/PRION:CVE-2022-21605 | PRION:CVE-2022-21604 3.3 https://vulners.com/prion/PRION:CVE-2022-21604 | PRION:CVE-2022-21599 3.3 https://vulners.com/prion/PRION:CVE-2022-21599 | PRION:CVE-2022-21594 3.3 https://vulners.com/prion/PRION:CVE-2022-21594 | PRION:CVE-2021-2307 3.3 https://vulners.com/prion/PRION:CVE-2021-2307\n| PRION:CVE-2023-21875 3.2 https://vulners.com/prion/PRION:CVE-2023-21875\n| PRION:CVE-2022-39403 3.0 https://vulners.com/prion/PRION:CVE-2022-39403\n| PRION:CVE-2022-21486 2.9 https://vulners.com/prion/PRION:CVE-2022-21486\n| PRION:CVE-2022-21485 2.9 https://vulners.com/prion/PRION:CVE-2022-21485 | PRION:CVE-2022-21484 2.9 https://vulners.com/prion/PRION:CVE-2022-21484\n| PRION:CVE-2022-21357 2.9 https://vulners.com/prion/PRION:CVE-2022-21357\n| PRION:CVE-2022-21355 2.9 https://vulners.com/prion/PRION:CVE-2022-21355 | PRION:CVE-2022-21333 2.9 https://vulners.com/prion/PRION:CVE-2022-21333 | PRION:CVE-2022-21331 2.9 https://vulners.com/prion/PRION:CVE-2022-21331\n| PRION:CVE-2022-21325 2.9 https://vulners.com/prion/PRION:CVE-2022-21325\n| PRION:CVE-2022-21324 2.9 https://vulners.com/prion/PRION:CVE-2022-21324\n| PRION:CVE-2022-21323 2.9 https://vulners.com/prion/PRION:CVE-2022-21323\n| PRION:CVE-2022-21321 2.9 https://vulners.com/prion/PRION:CVE-2022-21321 | PRION:CVE-2022-21319 2.9 https://vulners.com/prion/PRION:CVE-2022-21319\n| PRION:CVE-2022-21317 2.9 https://vulners.com/prion/PRION:CVE-2022-21317\n| PRION:CVE-2022-21313 2.9 https://vulners.com/prion/PRION:CVE-2022-21313 | PRION:CVE-2022-21312 2.9 https://vulners.com/prion/PRION:CVE-2022-21312 | PRION:CVE-2022-21311 2.9 https://vulners.com/prion/PRION:CVE-2022-21311\n| PRION:CVE-2019-2797 2.3 https://vulners.com/prion/PRION:CVE-2019-2797\n| PRION:CVE-2022-39402 2.1 https://vulners.com/prion/PRION:CVE-2022-39402\n| PRION:CVE-2022-21460 2.1 https://vulners.com/prion/PRION:CVE-2022-21460\n| PRION:CVE-2022-21451 2.1 https://vulners.com/prion/PRION:CVE-2022-21451 | PRION:CVE-2022-21444 2.1 https://vulners.com/prion/PRION:CVE-2022-21444\n| PRION:CVE-2021-35632 2.1 https://vulners.com/prion/PRION:CVE-2021-35632\n| PRION:CVE-2021-2042 2.1 https://vulners.com/prion/PRION:CVE-2021-2042 | PRION:CVE-2019-2969 2.1 https://vulners.com/prion/PRION:CVE-2019-2969 | PRION:CVE-2021-2232 1.9 https://vulners.com/prion/PRION:CVE-2021-2232\n| PRION:CVE-2019-2634 1.9 https://vulners.com/prion/PRION:CVE-2019-2634\n| PRION:CVE-2019-2535 1.9 https://vulners.com/prion/PRION:CVE-2019-2535\n| PRION:CVE-2018-3174 1.9 https://vulners.com/prion/PRION:CVE-2018-3174\n| PRION:CVE-2018-3084 1.9 https://vulners.com/prion/PRION:CVE-2018-3084\n| PRION:CVE-2023-22058 1.7 https://vulners.com/prion/PRION:CVE-2023-22058\n| PRION:CVE-2022-21625 1.7 https://vulners.com/prion/PRION:CVE-2022-21625\n| PRION:CVE-2022-21595 1.7 https://vulners.com/prion/PRION:CVE-2022-21595 | PRION:CVE-2019-2536 1.2 https://vulners.com/prion/PRION:CVE-2019-2536\n| PRION:CVE-2019-2513 1.2 https://vulners.com/prion/PRION:CVE-2019-2513\n|_ PRION:CVE-2022-21611 0.8 https://vulners.com/prion/PRION:CVE-2022-21611 8443/tcp closed https-alt conn-refused 30000/tcp closed ndmps conn-refused 30718/tcp closed unknown conn-refused 30951/tcp closed unknown conn-refused", "creation_timestamp": "2023-11-15T17:01:59.000000Z"}, {"uuid": "9fb7b43d-8eb1-46be-bbfb-2723d455c281", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-21325", "type": "published-proof-of-concept", "source": "https://t.me/BABATATASASA/5994", "content": "| PRION:CVE-2022-21605 3.3 https://vulners.com/prion/PRION:CVE-2022-21605 | PRION:CVE-2022-21604 3.3 https://vulners.com/prion/PRION:CVE-2022-21604 | PRION:CVE-2022-21599 3.3 https://vulners.com/prion/PRION:CVE-2022-21599 | PRION:CVE-2022-21594 3.3 https://vulners.com/prion/PRION:CVE-2022-21594 | PRION:CVE-2021-2307 3.3 https://vulners.com/prion/PRION:CVE-2021-2307\n| PRION:CVE-2023-21875 3.2 https://vulners.com/prion/PRION:CVE-2023-21875\n| PRION:CVE-2022-39403 3.0 https://vulners.com/prion/PRION:CVE-2022-39403\n| PRION:CVE-2022-21486 2.9 https://vulners.com/prion/PRION:CVE-2022-21486\n| PRION:CVE-2022-21485 2.9 https://vulners.com/prion/PRION:CVE-2022-21485 | PRION:CVE-2022-21484 2.9 https://vulners.com/prion/PRION:CVE-2022-21484\n| PRION:CVE-2022-21357 2.9 https://vulners.com/prion/PRION:CVE-2022-21357\n| PRION:CVE-2022-21355 2.9 https://vulners.com/prion/PRION:CVE-2022-21355 | PRION:CVE-2022-21333 2.9 https://vulners.com/prion/PRION:CVE-2022-21333 | PRION:CVE-2022-21331 2.9 https://vulners.com/prion/PRION:CVE-2022-21331\n| PRION:CVE-2022-21325 2.9 https://vulners.com/prion/PRION:CVE-2022-21325\n| PRION:CVE-2022-21324 2.9 https://vulners.com/prion/PRION:CVE-2022-21324\n| PRION:CVE-2022-21323 2.9 https://vulners.com/prion/PRION:CVE-2022-21323\n| PRION:CVE-2022-21321 2.9 https://vulners.com/prion/PRION:CVE-2022-21321 | PRION:CVE-2022-21319 2.9 https://vulners.com/prion/PRION:CVE-2022-21319\n| PRION:CVE-2022-21317 2.9 https://vulners.com/prion/PRION:CVE-2022-21317\n| PRION:CVE-2022-21313 2.9 https://vulners.com/prion/PRION:CVE-2022-21313 | PRION:CVE-2022-21312 2.9 https://vulners.com/prion/PRION:CVE-2022-21312 | PRION:CVE-2022-21311 2.9 https://vulners.com/prion/PRION:CVE-2022-21311\n| PRION:CVE-2019-2797 2.3 https://vulners.com/prion/PRION:CVE-2019-2797\n| PRION:CVE-2022-39402 2.1 https://vulners.com/prion/PRION:CVE-2022-39402\n| PRION:CVE-2022-21460 2.1 https://vulners.com/prion/PRION:CVE-2022-21460\n| PRION:CVE-2022-21451 2.1 https://vulners.com/prion/PRION:CVE-2022-21451 | PRION:CVE-2022-21444 2.1 https://vulners.com/prion/PRION:CVE-2022-21444\n| PRION:CVE-2021-35632 2.1 https://vulners.com/prion/PRION:CVE-2021-35632\n| PRION:CVE-2021-2042 2.1 https://vulners.com/prion/PRION:CVE-2021-2042 | PRION:CVE-2019-2969 2.1 https://vulners.com/prion/PRION:CVE-2019-2969 | PRION:CVE-2021-2232 1.9 https://vulners.com/prion/PRION:CVE-2021-2232\n| PRION:CVE-2019-2634 1.9 https://vulners.com/prion/PRION:CVE-2019-2634\n| PRION:CVE-2019-2535 1.9 https://vulners.com/prion/PRION:CVE-2019-2535\n| PRION:CVE-2018-3174 1.9 https://vulners.com/prion/PRION:CVE-2018-3174\n| PRION:CVE-2018-3084 1.9 https://vulners.com/prion/PRION:CVE-2018-3084\n| PRION:CVE-2023-22058 1.7 https://vulners.com/prion/PRION:CVE-2023-22058\n| PRION:CVE-2022-21625 1.7 https://vulners.com/prion/PRION:CVE-2022-21625\n| PRION:CVE-2022-21595 1.7 https://vulners.com/prion/PRION:CVE-2022-21595 | PRION:CVE-2019-2536 1.2 https://vulners.com/prion/PRION:CVE-2019-2536\n| PRION:CVE-2019-2513 1.2 https://vulners.com/prion/PRION:CVE-2019-2513\n|_ PRION:CVE-2022-21611 0.8 https://vulners.com/prion/PRION:CVE-2022-21611 8443/tcp closed https-alt conn-refused 30000/tcp closed ndmps conn-refused 30718/tcp closed unknown conn-refused 30951/tcp closed unknown conn-refused", "creation_timestamp": "2023-11-15T17:01:59.000000Z"}, {"uuid": "c997770f-0760-4f46-9368-9043d3fbbc78", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-21323", "type": "seen", "source": "https://t.me/cibsecurity/35858", "content": "\u203c CVE-2022-21323 \u203c\n\nVulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized read access to a subset of MySQL Cluster accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of MySQL Cluster. CVSS 3.1 Base Score 2.9 (Confidentiality and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:L).\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-01-19T14:41:59.000000Z"}, {"uuid": "6a5c3d03-8f34-40e9-9bfe-42d9e4c221f3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-21323", "type": "published-proof-of-concept", "source": "https://t.me/BABATATASASA/5994", "content": "| PRION:CVE-2022-21605 3.3 https://vulners.com/prion/PRION:CVE-2022-21605 | PRION:CVE-2022-21604 3.3 https://vulners.com/prion/PRION:CVE-2022-21604 | PRION:CVE-2022-21599 3.3 https://vulners.com/prion/PRION:CVE-2022-21599 | PRION:CVE-2022-21594 3.3 https://vulners.com/prion/PRION:CVE-2022-21594 | PRION:CVE-2021-2307 3.3 https://vulners.com/prion/PRION:CVE-2021-2307\n| PRION:CVE-2023-21875 3.2 https://vulners.com/prion/PRION:CVE-2023-21875\n| PRION:CVE-2022-39403 3.0 https://vulners.com/prion/PRION:CVE-2022-39403\n| PRION:CVE-2022-21486 2.9 https://vulners.com/prion/PRION:CVE-2022-21486\n| PRION:CVE-2022-21485 2.9 https://vulners.com/prion/PRION:CVE-2022-21485 | PRION:CVE-2022-21484 2.9 https://vulners.com/prion/PRION:CVE-2022-21484\n| PRION:CVE-2022-21357 2.9 https://vulners.com/prion/PRION:CVE-2022-21357\n| PRION:CVE-2022-21355 2.9 https://vulners.com/prion/PRION:CVE-2022-21355 | PRION:CVE-2022-21333 2.9 https://vulners.com/prion/PRION:CVE-2022-21333 | PRION:CVE-2022-21331 2.9 https://vulners.com/prion/PRION:CVE-2022-21331\n| PRION:CVE-2022-21325 2.9 https://vulners.com/prion/PRION:CVE-2022-21325\n| PRION:CVE-2022-21324 2.9 https://vulners.com/prion/PRION:CVE-2022-21324\n| PRION:CVE-2022-21323 2.9 https://vulners.com/prion/PRION:CVE-2022-21323\n| PRION:CVE-2022-21321 2.9 https://vulners.com/prion/PRION:CVE-2022-21321 | PRION:CVE-2022-21319 2.9 https://vulners.com/prion/PRION:CVE-2022-21319\n| PRION:CVE-2022-21317 2.9 https://vulners.com/prion/PRION:CVE-2022-21317\n| PRION:CVE-2022-21313 2.9 https://vulners.com/prion/PRION:CVE-2022-21313 | PRION:CVE-2022-21312 2.9 https://vulners.com/prion/PRION:CVE-2022-21312 | PRION:CVE-2022-21311 2.9 https://vulners.com/prion/PRION:CVE-2022-21311\n| PRION:CVE-2019-2797 2.3 https://vulners.com/prion/PRION:CVE-2019-2797\n| PRION:CVE-2022-39402 2.1 https://vulners.com/prion/PRION:CVE-2022-39402\n| PRION:CVE-2022-21460 2.1 https://vulners.com/prion/PRION:CVE-2022-21460\n| PRION:CVE-2022-21451 2.1 https://vulners.com/prion/PRION:CVE-2022-21451 | PRION:CVE-2022-21444 2.1 https://vulners.com/prion/PRION:CVE-2022-21444\n| PRION:CVE-2021-35632 2.1 https://vulners.com/prion/PRION:CVE-2021-35632\n| PRION:CVE-2021-2042 2.1 https://vulners.com/prion/PRION:CVE-2021-2042 | PRION:CVE-2019-2969 2.1 https://vulners.com/prion/PRION:CVE-2019-2969 | PRION:CVE-2021-2232 1.9 https://vulners.com/prion/PRION:CVE-2021-2232\n| PRION:CVE-2019-2634 1.9 https://vulners.com/prion/PRION:CVE-2019-2634\n| PRION:CVE-2019-2535 1.9 https://vulners.com/prion/PRION:CVE-2019-2535\n| PRION:CVE-2018-3174 1.9 https://vulners.com/prion/PRION:CVE-2018-3174\n| PRION:CVE-2018-3084 1.9 https://vulners.com/prion/PRION:CVE-2018-3084\n| PRION:CVE-2023-22058 1.7 https://vulners.com/prion/PRION:CVE-2023-22058\n| PRION:CVE-2022-21625 1.7 https://vulners.com/prion/PRION:CVE-2022-21625\n| PRION:CVE-2022-21595 1.7 https://vulners.com/prion/PRION:CVE-2022-21595 | PRION:CVE-2019-2536 1.2 https://vulners.com/prion/PRION:CVE-2019-2536\n| PRION:CVE-2019-2513 1.2 https://vulners.com/prion/PRION:CVE-2019-2513\n|_ PRION:CVE-2022-21611 0.8 https://vulners.com/prion/PRION:CVE-2022-21611 8443/tcp closed https-alt conn-refused 30000/tcp closed ndmps conn-refused 30718/tcp closed unknown conn-refused 30951/tcp closed unknown conn-refused", "creation_timestamp": "2023-11-15T17:01:59.000000Z"}, {"uuid": "bb2a6d17-45fe-4970-b596-bf725b1a3527", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-21325", "type": "seen", "source": "https://t.me/cibsecurity/35779", "content": "\u203c CVE-2022-21325 \u203c\n\nVulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized read access to a subset of MySQL Cluster accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of MySQL Cluster. CVSS 3.1 Base Score 2.9 (Confidentiality and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:L).\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-01-19T14:25:44.000000Z"}, {"uuid": "e1576f01-e109-487a-b61e-a78212a7cfa8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-21327", "type": "seen", "source": "https://t.me/cibsecurity/35841", "content": "\u203c CVE-2022-21327 \u203c\n\nVulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-01-19T14:39:06.000000Z"}, {"uuid": "0329d928-166c-4f69-ac23-826d6fba512a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-21326", "type": "seen", "source": "https://t.me/cibsecurity/35839", "content": "\u203c CVE-2022-21326 \u203c\n\nVulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-01-19T14:39:03.000000Z"}, {"uuid": "709a790c-b219-4996-ac12-68fbc51f9b09", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-21328", "type": "seen", "source": "https://t.me/cibsecurity/35787", "content": "\u203c CVE-2022-21328 \u203c\n\nVulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-01-19T14:26:00.000000Z"}]}