{"vulnerability": "cve-2024-4504", "sightings": [{"uuid": "67c1055a-4546-465d-82ff-bcb08be9b7de", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45045", "type": "seen", "source": "https://t.me/cvedetector/4431", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-45045 - Collabora Online Mobile JavaScript Endpoint Injection Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-45045 \nPublished : Aug. 29, 2024, 5:15 p.m. | 44\u00a0minutes ago \nDescription : Collabora Online is a collaborative online office suite based on LibreOffice technology. In the mobile (Android/iOS) device variants of Collabora Online it was possible to inject JavaScript via url encoded values in links contained in documents. Since the Android JavaScript interface allows access to internal functions, the likelihood that the app could be compromised via this vulnerability is considered high. Non-mobile variants are not affected. Mobile variants should update to the latest version provided by the platform appstore. There are no known workarounds for this vulnerability. \nSeverity: 6.3 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-29T20:24:26.000000Z"}, {"uuid": "e2bbc504-0e50-4939-a611-d06b9701e5ca", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45048", "type": "seen", "source": "https://t.me/cvedetector/4360", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-45048 - PHPSpreadsheet XXE Local File Information Disclosure Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-45048 \nPublished : Aug. 28, 2024, 9:15 p.m. | 42\u00a0minutes ago \nDescription : PHPSpreadsheet is a pure PHP library for reading and writing spreadsheet files. Affected versions are subject to a bypassing of a filter which allows for an XXE-attack. This in turn allows attacker to obtain contents of local files, even if error reporting is muted. This vulnerability has been addressed in release version 2.2.1. All users are advised to upgrade. There are no known workarounds for this vulnerability. \nSeverity: 8.8 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"28 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-29T00:19:47.000000Z"}, {"uuid": "4de7d129-ebfa-4d11-b61b-19ee34fb846b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45046", "type": "seen", "source": "https://t.me/cvedetector/4359", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-45046 - PHPSpreadsheet XSS Font Injection\", \n  \"Content\": \"CVE ID : CVE-2024-45046 \nPublished : Aug. 28, 2024, 9:15 p.m. | 42\u00a0minutes ago \nDescription : PHPSpreadsheet is a pure PHP library for reading and writing spreadsheet files. In affected versions `\\PhpOffice\\PhpSpreadsheet\\Writer\\Html` doesn't sanitize spreadsheet styling information such as font names, allowing an attacker to inject arbitrary JavaScript on the page. As a result an attacker may used a crafted spreadsheet to fully takeover a session of a user viewing spreadsheet files as HTML. This issue has been addressed in release version 2.1.0. All users are advised to upgrade. There are no known workarounds for this vulnerability. \nSeverity: 5.4 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"28 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-29T00:19:47.000000Z"}, {"uuid": "dbc31639-3146-478e-a252-e046aa64c49a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45049", "type": "seen", "source": "https://t.me/cvedetector/4283", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-45049 - Hydra Unauthenticated Evaluations\", \n  \"Content\": \"CVE ID : CVE-2024-45049 \nPublished : Aug. 27, 2024, 9:15 p.m. | 34\u00a0minutes ago \nDescription : Hydra is a Continuous Integration service for Nix based projects. It is possible to trigger evaluations in Hydra without any authentication. Depending on the size of evaluations, this can impact the availability of systems. The problem can be fixed by applying  to any Hydra package. Users are advised to upgrade. Users unable to upgrade should deny the `/api/push` route in a reverse proxy. This also breaks the \"Evaluate jobset\" button in the frontend. \nSeverity: 7.5 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"27 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-28T00:05:14.000000Z"}, {"uuid": "b9979045-d72a-412b-bcc3-e7b4772494af", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45040", "type": "seen", "source": "https://t.me/cvedetector/4963", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-45040 - Gnark Groth16 Commitment Zero-Knowledge Property Break\", \n  \"Content\": \"CVE ID : CVE-2024-45040 \nPublished : Sept. 6, 2024, 1:15 p.m. | 23\u00a0minutes ago \nDescription : gnark is a fast zk-SNARK library that offers a high-level API to design circuits. Prior to version 0.11.0, commitments to private witnesses in Groth16 as implemented break the zero-knowledge property. The vulnerability affects only Groth16 proofs with commitments. Notably, PLONK proofs are not affected. The vulnerability affects the zero-knowledge property of the proofs - in case the witness (secret or internal) values are small, then the attacker may be able to enumerate all possible choices to deduce the actual value. If the possible choices for the variables to be committed is large or there are many values committed, then it would be computationally infeasible to enumerate all valid choices. It doesn't affect the completeness/soundness of the proofs. The vulnerability has been fixed in version 0.11.0. The patch to fix the issue is to add additional randomized value to the list of committed value at proving time to mask the rest of the values which were committed. As a workaround, the user can manually commit to a randomized value. \nSeverity: 5.9 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"06 Sep 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-06T15:46:01.000000Z"}, {"uuid": "c74305c9-0d3c-4790-832a-be21d84bf309", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45046", "type": "seen", "source": "https://gist.github.com/alon710/9b9b997d8032789deeb3bfeaeab9a864", "content": "", "creation_timestamp": "2026-01-24T22:31:20.000000Z"}, {"uuid": "3d42d322-f897-450b-895f-54725302f6da", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45046", "type": "seen", "source": "https://gist.github.com/alon710/dcf37c30859ea3d4a2aa8bcebb05efea", "content": "", "creation_timestamp": "2026-01-24T22:31:17.000000Z"}, {"uuid": "a5e9561b-c61c-4e3f-9da1-ea80829d765b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45046", "type": "seen", "source": "https://gist.github.com/alon710/ad6e3803524ade6af5df3970192eee5d", "content": "", "creation_timestamp": "2026-01-24T22:31:35.000000Z"}, {"uuid": "e59a4884-6a3a-4a35-92ca-d55eec0cb9ab", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45046", "type": "seen", "source": "https://gist.github.com/alon710/6e354ec4eb1a9dba38411073888dc27f", "content": "", "creation_timestamp": "2026-01-24T22:31:33.000000Z"}, {"uuid": "911da659-2f48-48c0-abff-6b00bf040556", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45043", "type": "seen", "source": "https://t.me/cvedetector/4351", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-45043 - \"OpenTelemetry Collector AWS Firehose Receiver Unauthenticated Remote Request Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-45043 \nPublished : Aug. 28, 2024, 8:15 p.m. | 22\u00a0minutes ago \nDescription : The OpenTelemetry Collector module AWS firehose receiver is for ingesting AWS Kinesis Data Firehose delivery stream messages and parsing the records received based on the configured record type. `awsfirehosereceiver` allows unauthenticated remote requests, even when configured to require a key. OpenTelemetry Collector can be configured to receive CloudWatch metrics via an AWS Firehose Stream. Firehose sets the header `X-Amz-Firehose-Access-Key` with an arbitrary configured string. The OpenTelemetry Collector awsfirehosereceiver can optionally be configured to require this key on incoming requests. However, when this is configured it **still accepts incoming requests with no key**. Only OpenTelemetry Collector users configured with the \u201calpha\u201d `awsfirehosereceiver` module are affected. This module was added in version v0.49.0 of the \u201cContrib\u201d distribution (or may be included in custom builds). There is a risk of unauthorized users writing metrics. Carefully crafted metrics could hide other malicious activity. There is no risk of exfiltrating data. It\u2019s likely these endpoints will be exposed to the public internet, as Firehose does not support private HTTP endpoints. A fix was introduced in PR #34847 and released with v0.108.0. All users are advised to upgrade. There are no known workarounds for this vulnerability. \nSeverity: 5.3 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"28 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-28T22:39:24.000000Z"}, {"uuid": "0771b1b0-43f4-4bdf-9bb8-e3f08c5283f1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45047", "type": "seen", "source": "https://t.me/cvedetector/4536", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-45047 - Svelte Server-Side Rendering mXSS Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-45047 \nPublished : Aug. 30, 2024, 5:15 p.m. | 34\u00a0minutes ago \nDescription : svelte performance oriented web framework. A potential mXSS vulnerability exists in Svelte for versions up to but not including 4.2.19. Svelte improperly escapes HTML on server-side rendering. The assumption is that attributes will always stay as such, but in some situation the final DOM tree rendered on browsers is different from what Svelte expects on server-side rendering. This may be leveraged to perform XSS attacks, and a type of the XSS is known as mXSS (mutation XSS). More specifically, this can occur when injecting malicious content into an attribute within a `noscript` tag. This issue has been addressed in release version 4.2.19. Users are advised to upgrade. There are no known workarounds for this vulnerability. \nSeverity: 5.4 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"30 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-30T19:49:51.000000Z"}, {"uuid": "17b37db8-d640-410f-aa2c-12579f11a6ac", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45041", "type": "seen", "source": "https://t.me/cvedetector/5110", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-45041 - Kubernetes External Secrets Operator Token AbuseSkill Exploit\", \n  \"Content\": \"CVE ID : CVE-2024-45041 \nPublished : Sept. 9, 2024, 3:15 p.m. | 37\u00a0minutes ago \nDescription : External Secrets Operator is a Kubernetes operator that integrates external secret management systems. The external-secrets has a deployment called default-external-secrets-cert-controller, which is bound with a same-name ClusterRole. This ClusterRole has \"get/list\" verbs of secrets resources. It also has path/update verb of validatingwebhookconfigurations resources.  This can be used to abuse the SA token of the deployment to retrieve or get ALL secrets in the whole cluster, capture and log all data from requests attempting to update Secrets, or make a webhook deny all Pod create and update requests. This vulnerability is fixed in 0.10.2. \nSeverity: 8.3 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 Sep 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-09T18:09:34.000000Z"}, {"uuid": "69a71e2f-13fd-49f8-8db0-17b195af6c77", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45046", "type": "seen", "source": "https://gist.github.com/alon710/cb1843d2e4ad9145bc6956f3c0ebc6dd", "content": "", "creation_timestamp": "2026-01-24T21:24:30.000000Z"}, {"uuid": "789c2c30-a74e-4693-9b20-2b5d7cbc89a6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45044", "type": "seen", "source": "https://t.me/cvedetector/5240", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-45044 - Bareos Command Abbreviation Vulnerability (Authorization Bypass)\", \n  \"Content\": \"CVE ID : CVE-2024-45044 \nPublished : Sept. 10, 2024, 3:15 p.m. | 45\u00a0minutes ago \nDescription : Bareos is open source software for backup, archiving, and recovery of data for operating systems. When a command ACL is in place and a user executes a command in bconsole using an abbreviation (i.e. \"w\" for \"whoami\") the ACL check did not apply to the full form (i.e. \"whoami\") but to the abbreviated form (i.e. \"w\"). If the command ACL is configured with negative ACL that should forbid using the \"whoami\" command, you could still use \"w\" or \"who\" as a command successfully. Fixes for the problem are shipped in Bareos versions 23.0.4, 22.1.6 and 21.1.11. If only positive command ACLs are used without any negation, the problem does not occur. \nSeverity: 8.8 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"10 Sep 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-10T18:25:07.000000Z"}]}