https://vulnerability.circl.lu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Thu, 25 Jun 2026 05:35:50 +0000 https://vulnerability.circl.lu/sighting/657158f2-f022-42a1-8bf8-1d91c4618ff4/export {"uuid": "657158f2-f022-42a1-8bf8-1d91c4618ff4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-21485", "type": "seen", "source": "https://t.me/cibsecurity/41117", "content": "\u203c CVE-2022-21485 \u203c\n\nVulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.35 and prior, 7.5.25 and prior, 7.6.21 and prior and 8.0.28 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-04-20T00:24:47.000000Z"} {"uuid": "657158f2-f022-42a1-8bf8-1d91c4618ff4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-21485", "type": "seen", "source": "https://t.me/cibsecurity/41117", "content": "\u203c CVE-2022-21485 \u203c\n\nVulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.35 and prior, 7.5.25 and prior, 7.6.21 and prior and 8.0.28 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-04-20T00:24:47.000000Z"} https://vulnerability.circl.lu/sighting/657158f2-f022-42a1-8bf8-1d91c4618ff4/export Wed, 20 Apr 2022 00:24:47 +0000 https://vulnerability.circl.lu/sighting/f9d4a178-973a-4c30-a856-471513b43979/export {"uuid": "f9d4a178-973a-4c30-a856-471513b43979", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-21481", "type": "seen", "source": "https://t.me/cibsecurity/41133", "content": "\u203c CVE-2022-21481 \u203c\n\nVulnerability in the PeopleSoft Enterprise FIN Cash Management product of Oracle PeopleSoft (component: Financial Gateway). The supported version that is affected is 9.2. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise PeopleSoft Enterprise FIN Cash Management. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in PeopleSoft Enterprise FIN Cash Management, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of PeopleSoft Enterprise FIN Cash Management accessible data as well as unauthorized read access to a subset of PeopleSoft Enterprise FIN Cash Management accessible data. CVSS 3.1 Base Score 5.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N).\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-04-20T00:30:47.000000Z"} {"uuid": "f9d4a178-973a-4c30-a856-471513b43979", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-21481", "type": "seen", "source": "https://t.me/cibsecurity/41133", "content": "\u203c CVE-2022-21481 \u203c\n\nVulnerability in the PeopleSoft Enterprise FIN Cash Management product of Oracle PeopleSoft (component: Financial Gateway). The supported version that is affected is 9.2. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise PeopleSoft Enterprise FIN Cash Management. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in PeopleSoft Enterprise FIN Cash Management, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of PeopleSoft Enterprise FIN Cash Management accessible data as well as unauthorized read access to a subset of PeopleSoft Enterprise FIN Cash Management accessible data. CVSS 3.1 Base Score 5.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N).\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-04-20T00:30:47.000000Z"} https://vulnerability.circl.lu/sighting/f9d4a178-973a-4c30-a856-471513b43979/export Wed, 20 Apr 2022 00:30:47 +0000 https://vulnerability.circl.lu/sighting/9378e1bf-161f-41dc-8f68-eb74c3b3d576/export {"uuid": "9378e1bf-161f-41dc-8f68-eb74c3b3d576", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-2148", "type": "seen", "source": "https://t.me/cibsecurity/46390", "content": "\u203c CVE-2022-2148 \u203c\n\nThe LinkedIn Company Updates WordPress plugin through 1.5.3 does not sanitise and escape its settings, allowing high privilege users such as admin to perform cross-Site Scripting attacks even when the unfiltered_html capability is disallowed.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-07-17T14:27:48.000000Z"} {"uuid": "9378e1bf-161f-41dc-8f68-eb74c3b3d576", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-2148", "type": "seen", "source": "https://t.me/cibsecurity/46390", "content": "\u203c CVE-2022-2148 \u203c\n\nThe LinkedIn Company Updates WordPress plugin through 1.5.3 does not sanitise and escape its settings, allowing high privilege users such as admin to perform cross-Site Scripting attacks even when the unfiltered_html capability is disallowed.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-07-17T14:27:48.000000Z"} https://vulnerability.circl.lu/sighting/9378e1bf-161f-41dc-8f68-eb74c3b3d576/export Sun, 17 Jul 2022 14:27:48 +0000 https://vulnerability.circl.lu/sighting/a3ace9a8-10f7-48c2-bdd5-01988e8adef9/export {"uuid": "a3ace9a8-10f7-48c2-bdd5-01988e8adef9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-21485", "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": "a3ace9a8-10f7-48c2-bdd5-01988e8adef9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-21485", "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"} https://vulnerability.circl.lu/sighting/a3ace9a8-10f7-48c2-bdd5-01988e8adef9/export Wed, 15 Nov 2023 17:01:59 +0000 https://vulnerability.circl.lu/sighting/17f6856f-b1bf-4df9-be95-8e335f891a68/export {"uuid": "17f6856f-b1bf-4df9-be95-8e335f891a68", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-21484", "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": "17f6856f-b1bf-4df9-be95-8e335f891a68", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-21484", "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"} https://vulnerability.circl.lu/sighting/17f6856f-b1bf-4df9-be95-8e335f891a68/export Wed, 15 Nov 2023 17:01:59 +0000 https://vulnerability.circl.lu/sighting/2c47c803-2ced-427a-96a7-c2a32522da6c/export {"uuid": "2c47c803-2ced-427a-96a7-c2a32522da6c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-21486", "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": "2c47c803-2ced-427a-96a7-c2a32522da6c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-21486", "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"} https://vulnerability.circl.lu/sighting/2c47c803-2ced-427a-96a7-c2a32522da6c/export Wed, 15 Nov 2023 17:01:59 +0000