{"vulnerability": "CVE-2020-1075", "sightings": [{"uuid": "02deb2a8-badd-48ad-9f4f-087a49155831", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-10756", "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": "b9862bbc-3c64-41cb-b0a4-913c3270597c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-10758", "type": "seen", "source": "https://t.me/canyoupwnme/6619", "content": "Keycloak DoS - CVE-2020-10758\nhttps://www.soluble.ai/blog/keycloak-cve-2020-10758", "creation_timestamp": "2020-09-05T11:00:13.000000Z"}, {"uuid": "a560cb45-5e0a-4e5f-a512-e46acd75fe95", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-10756", "type": "seen", "source": "https://t.me/VulnerabilityNews/27428", "content": "It was discovered that the update for the virt:rhel module in the RHSA-2020:4676 (https://ift.tt/PRW3jtu) erratum released as part of Red Hat Enterprise Linux 8.3 failed to include the fix for the qemu-kvm component issue CVE-2020-10756, which was previously corrected in virt:rhel/qemu-kvm via erratum RHSA-2020:4059 (https://ift.tt/tqpc1GB). CVE-2021-20295 was assigned to that Red Hat specific security regression. For more details about the original security issue CVE-2020-10756, refer to bug 1835986 or the CVE page: https://ift.tt/kDXvcR8.\nPublished at: April 02, 2022 at 01:15AM\nView on website", "creation_timestamp": "2022-04-02T02:42:56.000000Z"}, {"uuid": "9325d54f-ea9c-46d6-8d57-db1d3fd21bdb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-10751", "type": "seen", "source": "https://t.me/VulnerabilityNews/16551", "content": "** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2020-10751. Reason: This candidate is a duplicate of CVE-2020-10751. Notes: All CVE users should reference CVE-2020-10751 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage.\nPublished at: August 14, 2020 at 10:15PM\nView on website", "creation_timestamp": "2020-08-15T00:46:14.000000Z"}, {"uuid": "c97c59de-92d6-4107-906f-4526f51f6652", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-10759", "type": "published-proof-of-concept", "source": "https://t.me/CyberSecurityTechnologies/1243", "content": "#Threat_Research\nLegacy LVFS S3 bucket takeover and CVE-2020-10759 fwupd signature verification bypass\nhttps://github.com/justinsteven/advisories/blob/master/2020_fwupd_dangling_s3_bucket_and_CVE-2020-10759_signature_verification_bypass.md", "creation_timestamp": "2021-01-03T19:43:02.000000Z"}, {"uuid": "b8792d49-43a2-4b9f-a736-467d87a2a20b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-10758", "type": "published-proof-of-concept", "source": "https://t.me/CyberSecurityTechnologies/1708", "content": "#exploit\nCVE-2020-10758:\nKeycloak webserver <v11.0.1, Red Hat SSO - Content-Length DoS (PoC)\nhttps://www.soluble.ai/blog/keycloak-cve-2020-10758", "creation_timestamp": "2022-06-08T21:28:20.000000Z"}, {"uuid": "a7cca855-a489-4c00-8c25-2b363a685998", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-10759", "type": "seen", "source": "https://t.me/CyberSecurityTechnologies/2759", "content": "#Analytics\n10 most exploited vulnerabilities of the week (feb 15-21)\nCVE-2021-3156 - Heap-Based Buffer Overflow in Sudo\nhttps://t.me/cybersecuritytechnologies/2577\nCVE-2021-1732 - Windows kernel 0-day exploit is used by BITTER APT\nhttps://t.me/cybersecuritytechnologies/2679\nCVE-2021-1647 - MS Defender RCE Vulnerability\nhttps://www.anquanke.com/post/id/231625\nCVE-2020-10759 - Dazed Blesbok\nhttps://t.me/cybersecuritytechnologies/1243\nCVE-2021-21976 - VMware Post-Auth RCE in vSphere Replication\nCVE-2021-3177 - Python 3 Buffer Overflow\nhttps://t.me/cybersecuritytechnologies/2740\nCVE-2020-8625 - A vulnerability in BIND's GSSAPI\nhttps://kb.isc.org/docs/cve-2020-8625\nCVE-2021-20655\nhttps://jvn.jp/en/jp/JVN58774946/index.html\nCVE-2021-1366 - A vulnerability in the interprocess communication channel of Cisco AnyConnect Secure Client\nhttps://www.coresecurity.com/core-labs/articles/analysis-cisco-anyconnect-posture-hostscan-local-privilege-escalation-cve-2021", "creation_timestamp": "2021-02-22T14:45:11.000000Z"}, {"uuid": "f16b28c7-14da-4b14-a637-f2b4fc78af37", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-10756", "type": "seen", "source": "https://t.me/cibsecurity/13370", "content": "ATENTION\u203c New - CVE-2020-10756\n\nAn out-of-bounds read vulnerability was found in the SLiRP networking implementation of the QEMU emulator. This flaw occurs in the icmp6_send_echoreply() routine while replying to an ICMP echo request, also known as ping. This flaw allows a malicious guest to leak the contents of the host memory, resulting in possible information disclosure. This flaw affects versions of libslirp before 4.3.1.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2020-07-09T20:55:22.000000Z"}, {"uuid": "3e261aca-3e97-4930-a260-93acb7a5afae", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-10755", "type": "seen", "source": "https://t.me/cibsecurity/12650", "content": "ATENTION\u203c New - CVE-2020-10755\n\nAn insecure-credentials flaw was found in all openstack-cinder versions before openstack-cinder 14.1.0, all openstack-cinder 15.x.x versions before openstack-cinder 15.2.0 and all openstack-cinder 16.x.x versions before openstack-cinder 16.1.0. When using openstack-cinder with the Dell EMC ScaleIO or VxFlex OS backend storage driver, credentials for the entire backend are exposed in the ``connection_info`` element in all Block Storage v3 Attachments API calls containing that element. This flaw enables an end-user to create a volume, make an API call to show the attachment detail information, and retrieve a username and password that may be used to connect to another user's volume. Additionally, these credentials are valid for the ScaleIO or VxFlex OS Management API, should an attacker discover the Management API endpoint. Source: OpenStack project\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2020-06-10T20:55:23.000000Z"}]}