{"vulnerability": "CVE-2024-5651", "sightings": [{"uuid": "09b47156-42a3-42ae-8ca3-b09ac296b6d1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56511", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/1175", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-56511\n\ud83d\udd39 Description: DataEase is an open source data visualization analysis tool. Prior to 2.10.4, there is a flaw in the authentication in the io.dataease.auth.filter.TokenFilter class, which can be bypassed and cause the risk of unauthorized access. In the io.dataease.auth.filter.TokenFilter class, \u201drequest.getRequestURI\u201c is used to obtain the request URL, and it is passed to the \"WhitelistUtils.match\" method to determine whether the URL request is an interface that does not require authentication. The \"match\" method filters semicolons, but this is not enough. When users set \"server.servlet.context-path\" when deploying products, there is still a risk of being bypassed, which can be bypassed by any whitelist prefix /geo/../context-path/. The vulnerability has been fixed in v2.10.4.\n\ud83d\udccf Published: 2025-01-10T15:19:13.173Z\n\ud83d\udccf Modified: 2025-01-10T16:40:28.039Z\n\ud83d\udd17 References:\n1. https://github.com/dataease/dataease/security/advisories/GHSA-9f69-p73j-m73x", "creation_timestamp": "2025-01-10T17:04:01.000000Z"}, {"uuid": "f200ee65-4d9d-4b89-872a-2f91f9f901dd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56519", "type": "seen", "source": "https://t.me/cvedetector/13712", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56519 - \"tcpdf SVG Font Family Injection Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-56519 \nPublished : Dec. 27, 2024, 5:15 a.m. | 26\u00a0minutes ago \nDescription : An issue was discovered in TCPDF before 6.8.0. setSVGStyles does not sanitize the SVG font-family attribute. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"27 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-27T06:47:20.000000Z"}, {"uuid": "4f1c570f-2d80-43c8-9b5b-8004f62f91c3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56513", "type": "seen", "source": "https://t.me/cvedetector/14234", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56513 - \"...Karmada Unrestricted Cluster Access\"\", \n  \"Content\": \"CVE ID : CVE-2024-56513 \nPublished : Jan. 3, 2025, 5:15 p.m. | 16\u00a0minutes ago \nDescription : Karmada is a Kubernetes management system that allows users to run cloud-native applications across multiple Kubernetes clusters and clouds. Prior to version 1.12.0, the PULL mode clusters registered with the `karmadactl register` command have excessive privileges to access control plane resources. By abusing these permissions, an attacker able to authenticate as the karmada-agent to a karmada cluster would be able to obtain administrative privileges over the entire federation system including all registered member clusters. Since Karmada v1.12.0, command `karmadactl register` restricts the access permissions of pull mode member clusters to control plane resources. This way, an attacker able to authenticate as the karmada-agent cannot control other member clusters in Karmada. As a workaround, one may restrict the access permissions of pull mode member clusters to control plane resources according to Karmada Component Permissions Docs. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"03 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-03T18:41:46.000000Z"}, {"uuid": "5a5c57ef-51af-4071-b494-a79b71244446", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56514", "type": "seen", "source": "https://t.me/cvedetector/14228", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56514 - Karmada TarSlip Vulnerability Allows File System Tampering\", \n  \"Content\": \"CVE ID : CVE-2024-56514 \nPublished : Jan. 3, 2025, 5:15 p.m. | 16\u00a0minutes ago \nDescription : Karmada is a Kubernetes management system that allows users to run cloud-native applications across multiple Kubernetes clusters and clouds. Prior to version 1.12.0, both in karmadactl and karmada-operator, it is possible to supply a filesystem path, or an HTTP(s) URL to retrieve the custom resource definitions(CRDs) needed by Karmada. The CRDs are downloaded as a gzipped tarfile and are vulnerable to a TarSlip vulnerability. An attacker able to supply a malicious CRD file into a Karmada initialization could write arbitrary files in arbitrary paths of the filesystem. From Karmada version 1.12.0, when processing custom CRDs files, CRDs archive verification is utilized to enhance file system robustness. A workaround is available. Someone who needs to set flag `--crd` to customize the CRD files required for Karmada initialization when using `karmadactl init` to set up Karmada can manually inspect the CRD files to check whether they contain sequences such as `../` that would alter file paths, to determine if they potentially include malicious files. When using karmada-operator to set up Karmada, one must upgrade one's karmada-operator to one of the fixed versions. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"03 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-03T18:41:39.000000Z"}, {"uuid": "799f39c7-4ac4-4e14-9176-93810cae9275", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-5651", "type": "published-proof-of-concept", "source": "https://t.me/HackingInsights/9581", "content": "\u200aCVE-2024-5651: RCE Vulnerability in Fence Agents Exposes Critical Infrastructure to Exploitation\n\nhttps://securityonline.info/cve-2024-5651-rce-vulnerability-in-fence-agents-exposes-critical-infrastructure-to-exploitation/", "creation_timestamp": "2024-08-12T17:17:25.000000Z"}, {"uuid": "e8f5eed9-f1be-4a31-b50d-e0d2e7b0a3fd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56513", "type": "seen", "source": "https://t.me/CyberBulletin/9358", "content": "\u26a1\ufe0fCVE-2024-56513: Karmada Vulnerability Grants Attackers Control of Kubernetes Systems.\n\n#CyberBulletin", "creation_timestamp": "2025-01-06T06:36:06.000000Z"}, {"uuid": "76c4a270-310d-4944-b30b-51a621eab7a5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56510", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113721140557456523", "content": "", "creation_timestamp": "2024-12-26T21:01:36.206874Z"}, {"uuid": "fcb4de50-dfb8-45bd-83f3-07eb704f7c6a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56519", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113722915467001021", "content": "", "creation_timestamp": "2024-12-27T04:32:59.275065Z"}, {"uuid": "ce7407e0-6710-4e83-a14a-6f9cb61b2f10", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56519", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113722933136383974", "content": "", "creation_timestamp": "2024-12-27T04:37:28.829080Z"}, {"uuid": "7706e85a-01ce-4418-92b3-94e368c9f071", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56519", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lebaav3a432i", "content": "", "creation_timestamp": "2024-12-27T05:15:39.962068Z"}, {"uuid": "fb2ed10f-e48f-44c2-982b-7fc6b48de997", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56512", "type": "seen", "source": "https://bsky.app/profile/infosec.skyfleet.blue/post/3ledw3yyvwx22", "content": "", "creation_timestamp": "2024-12-28T06:51:58.023674Z"}, {"uuid": "b6b74e08-cd74-42bb-8036-4348c22c133e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56511", "type": "seen", "source": "https://bsky.app/profile/infosec.skyfleet.blue/post/3lfoarsbxvz2r", "content": "", "creation_timestamp": "2025-01-14T02:54:55.797158Z"}, {"uuid": "17d81c7f-63b6-46fb-81e3-b61c84eb97c7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56512", "type": "confirmed", "source": "https://github.com/projectdiscovery/nuclei-templates/tree/main/http/cves/2024/CVE-2024-56512.yaml", "content": "", "creation_timestamp": "2025-01-07T14:32:51.000000Z"}, {"uuid": "5a30111b-d28d-41e6-b8d2-24b148a36b13", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56513", "type": "seen", "source": "MISP/dd71e3c5-20f7-409a-8bcc-8df3cd8022a7", "content": "", "creation_timestamp": "2025-09-03T13:30:06.000000Z"}, {"uuid": "3e8461bd-c3f6-4363-b293-5c20b151b2cb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56518", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12271", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-56518\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: Hazelcast Management Center through 6.0 allows remote code execution via a JndiLoginModule user.provider.url in a hazelcast-client XML document (aka a client configuration file), which can be uploaded at the /cluster-connections URI.\n\ud83d\udccf Published: 2025-04-17T00:00:00.000Z\n\ud83d\udccf Modified: 2025-04-17T16:12:30.676Z\n\ud83d\udd17 References:\n1. https://docs.hazelcast.com/management-center/6.0-snapshot/getting-started/install\n2. https://gist.github.com/azraelxuemo/c3d42739aa3306a41111ef603dc65b4c", "creation_timestamp": "2025-04-17T16:58:31.000000Z"}, {"uuid": "218a823a-d377-4c11-b3bc-d192c3fae4da", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56513", "type": "seen", "source": "https://t.me/CyberBulletin/1945", "content": "\u26a1\ufe0fCVE-2024-56513: Karmada Vulnerability Grants Attackers Control of Kubernetes Systems.\n\n#CyberBulletin", "creation_timestamp": "2025-01-05T11:52:46.000000Z"}, {"uuid": "73c0fcea-cf28-4b1e-a3b7-cd7182cde0de", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56517", "type": "seen", "source": "https://t.me/cvedetector/13940", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56517 - \"LGSL Reflected Cross-Site Scripting Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-56517 \nPublished : Dec. 30, 2024, 5:15 p.m. | 44\u00a0minutes ago \nDescription : LGSL (Live Game Server List) provides online status lists for online video games. Versions up to and including 6.2.1 contain a reflected cross-site scripting vulnerability in the `Referer` HTTP header. The vulnerability allows attackers to inject arbitrary JavaScript code, which is reflected in the HTML response without proper sanitization. When crafted malicious input is provided in the `Referer` header, it is echoed back into an HTML attribute in the application\u2019s response. Commit 7ecb839df9358d21f64cdbff5b2536af25a77de1 contains a patch for the issue. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"30 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-30T19:18:33.000000Z"}, {"uuid": "54ec5146-3c1f-4fb5-8c8b-c16fe1d206cc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56516", "type": "seen", "source": "https://t.me/cvedetector/13939", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56516 - Free-one-api MD5 Password Hashing Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-56516 \nPublished : Dec. 30, 2024, 5:15 p.m. | 44\u00a0minutes ago \nDescription : free-one-api allows users to access large language model reverse engineering libraries through the standard OpenAI API format. In versions up to and including 1.0.1, MD5 is used to hash passwords before sending them to the backend. MD5 is a cryptographically broken hashing algorithm and is no longer considered secure for password storage or transmission. It is vulnerable to collision attacks and can be easily cracked using modern hardware, exposing user credentials to potential compromise. As of time of publication, a replacement for MD5 has not been committed to the free-one-api GitHub repository. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"30 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-30T19:18:32.000000Z"}, {"uuid": "dc484674-ec9d-467a-ace5-64b774c2075c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56510", "type": "seen", "source": "https://t.me/cvedetector/13695", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56510 - Marp Core XSSInjection\", \n  \"Content\": \"CVE ID : CVE-2024-56510 \nPublished : Dec. 26, 2024, 9:15 p.m. | 42\u00a0minutes ago \nDescription : @marp-team/marp-core is the core for Marp, which is the ecosystem to write your presentation with plain Markdown. Marp Core from v3.0.2 to v3.9.0 and v4.0.0, are vulnerable to cross-site scripting (XSS) due to improper neutralization of HTML sanitization. Marp Core v3.9.1 and v4.0.1 have been patched to fix that. If you are unable to update the package immediately, disable all HTML tags by setting html: false option in the Marp class constructor. \nSeverity: 5.3 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"26 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-26T23:15:43.000000Z"}, {"uuid": "e2d08fb1-f82d-40fb-aeee-56da1b1e7a8c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56513", "type": "seen", "source": "https://t.me/CyberBulletin/27050", "content": "\u26a1\ufe0fCVE-2024-56513: Karmada Vulnerability Grants Attackers Control of Kubernetes Systems.\n\n#CyberBulletin", "creation_timestamp": "2025-01-05T11:46:05.000000Z"}, {"uuid": "c36677db-ff1d-4207-be4a-10accf70e948", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56511", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113804747142398699", "content": "", "creation_timestamp": "2025-01-10T15:23:51.321375Z"}, {"uuid": "3752e3ef-aa21-4b78-8467-f6f71dc496bc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56513", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113765323783466999", "content": "", "creation_timestamp": "2025-01-03T16:17:58.775988Z"}, {"uuid": "a9988968-0f8a-419f-bc46-66907c027629", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56514", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113765323798362968", "content": "", "creation_timestamp": "2025-01-03T16:17:58.991876Z"}, {"uuid": "9c4a6ca4-bce4-4634-8e2b-5fca7ebc2990", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56513", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/113770707250738515", "content": "", "creation_timestamp": "2025-01-04T15:08:40.134391Z"}, {"uuid": "0ef65a5b-81d5-46bd-b3a6-517c5a3ea506", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56513", "type": "seen", "source": "https://bsky.app/profile/getpokemon7.bsky.social/post/3lf2dg3fjqc2i", "content": "", "creation_timestamp": "2025-01-06T04:48:53.302387Z"}, {"uuid": "2cf37895-8b00-4f86-b629-0aa4f0781f28", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56511", "type": "seen", "source": "Telegram/Ae4a-7LZgDUT9R61I3HEpK06HPHIjPCPLsnM4Z2Lzvo3M84A", "content": "", "creation_timestamp": "2025-02-20T23:26:55.000000Z"}, {"uuid": "7feffb97-8a9d-45c1-a86f-fadf1f63eac9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56511", "type": "seen", "source": "https://t.me/cvedetector/14967", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56511 - DataEase Unauthorized Access Bypass Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-56511 \nPublished : Jan. 10, 2025, 4:15 p.m. | 38\u00a0minutes ago \nDescription : DataEase is an open source data visualization analysis tool. Prior to 2.10.4, there is a flaw in the authentication in the io.dataease.auth.filter.TokenFilter class, which can be bypassed and cause the risk of unauthorized access. In the io.dataease.auth.filter.TokenFilter class, \u201drequest.getRequestURI\u201c is used to obtain the request URL, and it is passed to the \"WhitelistUtils.match\" method to determine whether the URL request is an interface that does not require authentication. The \"match\" method filters semicolons, but this is not enough. When users set \"server.servlet.context-path\" when deploying products, there is still a risk of being bypassed, which can be bypassed by any whitelist prefix /geo/../context-path/. The vulnerability has been fixed in v2.10.4. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"10 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-10T18:00:49.000000Z"}, {"uuid": "e3766426-c1eb-4f8f-a785-547cc8b1c442", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56512", "type": "seen", "source": "https://t.me/cvedetector/13847", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56512 - Apache NiFi Parameter Context and Controller Service Authorization Bypass\", \n  \"Content\": \"CVE ID : CVE-2024-56512 \nPublished : Dec. 28, 2024, 5:15 p.m. | 30\u00a0minutes ago \nDescription : Apache NiFi 1.10.0 through 2.0.0 are missing fine-grained authorization checking for Parameter Contexts, referenced Controller Services, and referenced Parameter Providers, when creating new Process Groups.  \n  \nCreating a new Process Group can include binding to a Parameter Context, but in cases where the Process Group did not reference any Parameter values, the framework did not check user authorization for the bound Parameter Context. Missing authorization for a bound Parameter Context enabled clients to download non-sensitive Parameter values after creating the Process Group.  \n  \nCreating a new Process Group can also include referencing existing Controller Services or Parameter Providers. The framework did not check user authorization for referenced Controller Services or Parameter Providers, enabling clients to create Process Groups and use these components that were otherwise unauthorized.  \n  \nThis vulnerability is limited in scope to authenticated users authorized to create Process Groups. The scope is further limited to deployments with component-based authorization policies. Upgrading to Apache NiFi 2.1.0 is the recommended mitigation, which includes authorization checking for Parameter and Controller Service references on Process Group creation. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"28 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-28T18:47:58.000000Z"}, {"uuid": "724c0afe-2ea6-4bbd-8c95-41c225eb931b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56512", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113731368868060448", "content": "", "creation_timestamp": "2024-12-28T16:22:48.050426Z"}, {"uuid": "f09ad0d6-ffa0-40fc-b35a-0b7e96116d2d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56512", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3leeywwuo572a", "content": "", "creation_timestamp": "2024-12-28T17:15:29.095623Z"}, {"uuid": "025aefac-c8ea-406c-9caf-3d276665155d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56511", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lffloqc5nu2l", "content": "", "creation_timestamp": "2025-01-10T16:16:06.188289Z"}, {"uuid": "03883a1e-bdb3-4f7e-a675-224d17765822", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56516", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113742729529291973", "content": "", "creation_timestamp": "2024-12-30T16:31:57.761316Z"}, {"uuid": "3dc6c36a-f7de-4695-a205-5ce1518113a0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56517", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113742766801800257", "content": "", "creation_timestamp": "2024-12-30T16:41:26.499544Z"}, {"uuid": "d018924a-b21c-4405-a6f9-49b1fd77e320", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56515", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lfv3vjtn5y2n", "content": "", "creation_timestamp": "2025-01-16T20:16:10.169954Z"}, {"uuid": "044739fa-28ed-4e5b-a263-94085315e04d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56511", "type": "seen", "source": "MISP/3445a876-cced-4346-bf37-e276ba39cff4", "content": "", "creation_timestamp": "2025-09-02T18:30:14.000000Z"}, {"uuid": "7c0e21d6-88cf-4aa5-9bfb-8ec1a3dea602", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56512", "type": "seen", "source": "MISP/3445a876-cced-4346-bf37-e276ba39cff4", "content": "", "creation_timestamp": "2025-09-02T18:30:14.000000Z"}]}