https://vulnerability.circl.lu/sightings/feed 2026-09-28T22:48:35.726451+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/6f44bf38-85cc-4c47-9f05-4f2e0c0acf38/export 2026-09-28T22:48:35.768913+00:00 Automation user https://vulnerability.circl.lu/user/automation {"uuid": "6f44bf38-85cc-4c47-9f05-4f2e0c0acf38", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-31025", "type": "seen", "source": "https://bsky.app/profile/ferramentaslinux.bsky.social/post/3m365n3idx22e", "content": "", "creation_timestamp": "2025-10-14T16:30:21.184086Z"} 2025-10-14T16:30:21.184086+00:00 https://vulnerability.circl.lu/sighting/f0c0a4fc-f58d-401a-b4d2-d07b20856c1c/export 2026-09-28T22:48:35.772058+00:00 Automation user https://vulnerability.circl.lu/user/automation {"uuid": "f0c0a4fc-f58d-401a-b4d2-d07b20856c1c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-31022", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15529", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2022-31022\n\ud83d\udd25 CVSS Score: 6.2 (cvssV3_1, Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N)\n\ud83d\udd39 Description: Bleve is a text indexing library for go. Bleve includes HTTP utilities under bleve/http package, that are used by its sample application. These HTTP methods pave way for exploitation of a node\u2019s filesystem where the bleve index resides, if the user has used bleve\u2019s own HTTP (bleve/http) handlers for exposing the access to the indexes. For instance, the CreateIndexHandler (`http/index_create.go`) and DeleteIndexHandler (`http/index_delete.go`) enable an attacker to create a bleve index (directory structure) anywhere where the user running the server has the write permissions and to delete recursively any directory owned by the same user account. Users who have used the bleve/http package for exposing access to bleve index without the explicit \nhandling for the Role Based Access Controls(RBAC) of the index assets would be impacted by this issue. Version 2.5.0 relocated the `http/` dir used _only_ by bleve-explorer to `blevesearch/bleve-explorer`, thereby addressing the issue. However, the http package is purely intended to be used for demonstration purposes. Bleve was never designed handle the RBACs, nor it was ever advertised to be used in that way. The collaborators of this project have decided to stay away from adding any authentication or authorization to bleve project at the moment. The bleve/http package is mainly for demonstration purposes and it lacks exhaustive validation of the user inputs as well as any authentication and authorization measures. It is recommended to not use bleve/http in production use cases.\n\ud83d\udccf Published: 2022-06-01T19:45:12.000Z\n\ud83d\udccf Modified: 2025-05-08T13:44:47.369Z\n\ud83d\udd17 References:\n1. https://github.com/blevesearch/bleve/security/advisories/GHSA-9w9f-6mg8-jp7w\n2. https://github.com/blevesearch/bleve/commit/1c7509d6a17d36f265c90b4e8f4e3a3182fe79ff\n3. https://github.com/blevesearch/bleve/commit/af9e3111dadfedf9d30f0448506b4a57fecc8550", "creation_timestamp": "2025-05-08T14:23:27.000000Z"} 2025-05-08T14:23:27+00:00 https://vulnerability.circl.lu/sighting/c64cf078-3b22-42d8-8099-8d877b8f9324/export 2026-09-28T22:48:35.772214+00:00 Automation user https://vulnerability.circl.lu/user/automation {"uuid": "c64cf078-3b22-42d8-8099-8d877b8f9324", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-31021", "type": "seen", "source": "https://t.me/ctinow/182556", "content": "https://ift.tt/9U6awQM\nCVE-2022-31021 | Hyperledger ursa up to 0.3.7 unknown vulnerability (GHSA-2q6j-gqc4-4gw3)", "creation_timestamp": "2024-02-10T14:46:08.000000Z"} 2024-02-10T14:46:08+00:00 https://vulnerability.circl.lu/sighting/0f0c34f7-7b20-4de3-b993-f2438d36efb8/export 2026-09-28T22:48:35.772331+00:00 Automation user https://vulnerability.circl.lu/user/automation {"uuid": "0f0c34f7-7b20-4de3-b993-f2438d36efb8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-31021", "type": "seen", "source": "https://t.me/ctinow/173008", "content": "https://ift.tt/HP6eACc\nCVE-2022-31021 Exploit", "creation_timestamp": "2024-01-24T19:16:38.000000Z"} 2024-01-24T19:16:38+00:00 https://vulnerability.circl.lu/sighting/2fb63ca0-22cd-48a1-894e-6fd7cd246038/export 2026-09-28T22:48:35.772430+00:00 Automation user https://vulnerability.circl.lu/user/automation {"uuid": "2fb63ca0-22cd-48a1-894e-6fd7cd246038", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-31020", "type": "seen", "source": "https://t.me/cibsecurity/49324", "content": "\u203c CVE-2022-31020 \u203c\n\nIndy Node is the server portion of a distributed ledger purpose-built for decentralized identity. In versions 1.12.4 and prior, the `pool-upgrade` request handler in Indy-Node allows an improperly authenticated attacker to remotely execute code on nodes within the network. The `pool-upgrade` request handler in Indy-Node 1.12.5 has been updated to properly authenticate pool-upgrade transactions before any processing is performed by the request handler. The transactions are further sanitized to prevent remote code execution. As a workaround, endorsers should not create DIDs for untrusted users. A vulnerable ledger should configure `auth_rules` to prevent new DIDs from being written to the ledger until the network can be upgraded.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-09-06T20:13:38.000000Z"} 2022-09-06T20:13:38+00:00 https://vulnerability.circl.lu/sighting/ce8bc018-e4f5-4d86-b4c5-01e61755eb86/export 2026-09-28T22:48:35.772534+00:00 Automation user https://vulnerability.circl.lu/user/automation {"uuid": "ce8bc018-e4f5-4d86-b4c5-01e61755eb86", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-31027", "type": "seen", "source": "https://t.me/cibsecurity/44089", "content": "\u203c CVE-2022-31027 \u203c\n\nOAuthenticator is an OAuth token library for the JupyerHub login handler. CILogonOAuthenticator is provided by the OAuthenticator package, and lets users log in to a JupyterHub via CILogon. This is primarily used to restrict a JupyterHub only to users of a given institute. The allowed_idps configuration trait of CILogonOAuthenticator is documented to be a list of domains that indicate the institutions whose users are authorized to access this JupyterHub. This authorization is validated by ensuring that the *email* field provided to us by CILogon has a *domain* that matches one of the domains listed in `allowed_idps`.If `allowed_idps` contains `berkeley.edu`, you might expect only users with valid current credentials provided by University of California, Berkeley to be able to access the JupyterHub. However, CILogonOAuthenticator does *not* verify which provider is used by the user to login, only the email address provided. So a user can login with a GitHub account that has email set to `@berkeley.edu`, and that will be treated exactly the same as someone logging in using the UC Berkeley official Identity Provider. The patch fixing this issue makes a *breaking change* in how `allowed_idps` is interpreted. It's no longer a list of domains, but configuration representing the `EntityID` of the IdPs that are allowed, picked from the [list maintained by CILogon](https://cilogon.org/idplist/). Users are advised to upgrade.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-06-09T16:33:23.000000Z"} 2022-06-09T16:33:23+00:00 https://vulnerability.circl.lu/sighting/a61d5b3f-05a3-4f48-a5cb-f948da73ccb7/export 2026-09-28T22:48:35.772641+00:00 Automation user https://vulnerability.circl.lu/user/automation {"uuid": "a61d5b3f-05a3-4f48-a5cb-f948da73ccb7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-31026", "type": "seen", "source": "https://t.me/cibsecurity/44085", "content": "\u203c CVE-2022-31026 \u203c\n\nTrilogy is a client library for MySQL. When authenticating, a malicious server could return a specially crafted authentication packet, causing the client to read and return up to 12 bytes of data from an uninitialized variable in stack memory. Users of the trilogy gem should upgrade to version 2.1.1 This issue can be avoided by only connecting to trusted servers.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-06-09T16:33:18.000000Z"} 2022-06-09T16:33:18+00:00 https://vulnerability.circl.lu/sighting/18782bd0-b06b-4b87-b722-812d76b5b7f1/export 2026-09-28T22:48:35.772747+00:00 Automation user https://vulnerability.circl.lu/user/automation {"uuid": "18782bd0-b06b-4b87-b722-812d76b5b7f1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-31028", "type": "seen", "source": "https://t.me/cibsecurity/43932", "content": "\u203c CVE-2022-31028 \u203c\n\nMinIO is a multi-cloud object storage solution. Starting with version RELEASE.2019-09-25T18-25-51Z and ending with version RELEASE.2022-06-02T02-11-04Z, MinIO is vulnerable to an unending go-routine buildup while keeping connections established due to HTTP clients not closing the connections. Public-facing MinIO deployments are most affected. Users should upgrade to RELEASE.2022-06-02T02-11-04Z to receive a patch. One possible workaround is to use a reverse proxy to limit the number of connections being attempted in front of MinIO, and actively rejecting connections from such malicious clients.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-06-07T20:31:07.000000Z"} 2022-06-07T20:31:07+00:00 https://vulnerability.circl.lu/sighting/784a6a07-9d96-43ab-8ec9-5802c5dd54e4/export 2026-09-28T22:48:35.772846+00:00 Automation user https://vulnerability.circl.lu/user/automation {"uuid": "784a6a07-9d96-43ab-8ec9-5802c5dd54e4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-31025", "type": "seen", "source": "https://t.me/cibsecurity/43925", "content": "\u203c CVE-2022-31025 \u203c\n\nDiscourse is an open source platform for community discussion. Prior to version 2.8.4 on the `stable` branch and 2.9.0beta5 on the `beta` and `tests-passed` branches, inviting users on sites that use single sign-on could bypass the `must_approve_users` check and invites by staff are always approved automatically. The issue is patched in Discourse version 2.8.4 on the `stable` branch and version `2.9.0.beta5` on the `beta` and `tests-passed` branches. As a workaround, disable invites or increase `min_trust_level_to_allow_invite` to reduce the attack surface to more trusted users.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-06-07T18:30:58.000000Z"} 2022-06-07T18:30:58+00:00 https://vulnerability.circl.lu/sighting/7029be14-543e-4ec4-ab7e-1e8955116d86/export 2026-09-28T22:48:35.772948+00:00 Automation user https://vulnerability.circl.lu/user/automation {"uuid": "7029be14-543e-4ec4-ab7e-1e8955116d86", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-31024", "type": "seen", "source": "https://t.me/cibsecurity/43767", "content": "\u203c CVE-2022-31024 \u203c\n\nrichdocuments is the repository for NextCloud Collabra, the app for Nextcloud Office collaboration. Prior to versions 6.0.0, 5.0.4, and 4.2.6, a user could be tricked into working against a remote Office by sending them a federated share. richdocuments versions 6.0.0, 5.0.4 and 4.2.6 contain a fix for this issue. There are currently no known workarounds available.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-06-02T22:26:02.000000Z"} 2022-06-02T22:26:02+00:00