{"vulnerability": "cve-2024-4581", "sightings": [{"uuid": "2bff2519-f819-4d03-a21e-c5ee1d5d8d80", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-45818", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3ldntz26p6s2s", "content": "", "creation_timestamp": "2024-12-19T12:15:56.687757Z"}, {"uuid": "7cfb64e1-af01-42dc-909b-aa58ea252f90", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-45819", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3ldntz4q5tq2v", "content": "", "creation_timestamp": "2024-12-19T12:15:59.562333Z"}, {"uuid": "6a0b7bf9-bbb7-4ec2-90f1-e06f0aaddada", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-45818", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113679408646274887", "content": "", "creation_timestamp": "2024-12-19T12:08:37.770472Z"}, {"uuid": "80888772-d6c6-4e81-ba85-627c1cb0b1c5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-45819", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113679408681284679", "content": "", "creation_timestamp": "2024-12-19T12:08:38.233743Z"}, {"uuid": "de708bd0-b5b5-416c-9baa-2e0c63de20b1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-45812", "type": "seen", "source": "https://gist.github.com/Wbaker7702/53198661ba029cb1af08a9ce551dbeb5", "content": "", "creation_timestamp": "2025-10-14T05:07:38.000000Z"}, {"uuid": "dbbcd01a-47bf-45b1-848f-334c6fd43387", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-45817", "type": "seen", "source": "https://t.me/cvedetector/6306", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-45817 - Xen APIC races: Lock Deadlock via Recursive Error Interrupt\", \n  \"Content\": \"CVE ID : CVE-2024-45817 \nPublished : Sept. 25, 2024, 11:15 a.m. | 41\u00a0minutes ago \nDescription : In x86's APIC (Advanced Programmable Interrupt Controller) architecture,  \nerror conditions are reported in a status register.  Furthermore, the OS  \ncan opt to receive an interrupt when a new error occurs.  \n  \nIt is possible to configure the error interrupt with an illegal vector,  \nwhich generates an error when an error interrupt is raised.  \n  \nThis case causes Xen to recurse through vlapic_error().  The recursion  \nitself is bounded; errors accumulate in the the status register and only  \ngenerate an interrupt when a new status bit becomes set.  \n  \nHowever, the lock protecting this state in Xen will try to be taken  \nrecursively, and deadlock. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"25 Sep 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-25T14:19:23.000000Z"}, {"uuid": "9d32e3c0-5170-4615-9ff3-fc0f9a45428b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-45818", "type": "seen", "source": "MISP/acd0294c-4561-4286-a04e-5c02a1c67b1f", "content": "", "creation_timestamp": "2025-09-15T13:28:32.000000Z"}, {"uuid": "47d03d05-d624-4ab4-838f-df97cd9ca46b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-45818", "type": "seen", "source": "MISP/acd0294c-4561-4286-a04e-5c02a1c67b1f", "content": "", "creation_timestamp": "2025-09-16T03:45:02.000000Z"}, {"uuid": "c0eacc65-349d-4941-a76f-15f4bd745c4e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-45818", "type": "seen", "source": "https://t.me/cvedetector/13321", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-45818 - Xen Hypervisor Deadlock Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-45818 \nPublished : Dec. 19, 2024, 12:15 p.m. | 41\u00a0minutes ago \nDescription : The hypervisor contains code to accelerate VGA memory accesses for HVM  \nguests, when the (virtual) VGA is in \"standard\" mode.  Locking involved  \nthere has an unusual discipline, leaving a lock acquired past the  \nreturn from the function that acquired it.  This behavior results in a  \nproblem when emulating an instruction with two memory accesses, both of  \nwhich touch VGA memory (plus some further constraints which aren't  \nrelevant here).  When emulating the 2nd access, the lock that is already  \nbeing held would be attempted to be re-acquired, resulting in a  \ndeadlock.  \n  \nThis deadlock was already found when the code was first introduced, but  \nwas analysed incorrectly and the fix was incomplete.  Analysis in light  \nof the new finding cannot find a way to make the existing locking  \ndiscipline work.  \n  \nIn staging, this logic has all been removed because it was discovered  \nto be accidentally disabled since Xen 4.7.  Therefore, we are fixing the  \nlocking problem by backporting the removal of most of the feature.  Note  \nthat even with the feature disabled, the lock would still be acquired  \nfor any accesses to the VGA MMIO region. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"19 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-19T13:58:58.000000Z"}, {"uuid": "a9daa88c-cdbc-4e9e-a559-a7c0ab900092", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-45819", "type": "seen", "source": "https://t.me/cvedetector/13322", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-45819 - Citrix Hypervisor Guests ACPI Table Memory Information Disclosure\", \n  \"Content\": \"CVE ID : CVE-2024-45819 \nPublished : Dec. 19, 2024, 12:15 p.m. | 41\u00a0minutes ago \nDescription : PVH guests have their ACPI tables constructed by the toolstack.  The  \nconstruction involves building the tables in local memory, which are  \nthen copied into guest memory.  While actually used parts of the local  \nmemory are filled in correctly, excess space that is being allocated is  \nleft with its prior contents. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"19 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-19T13:58:59.000000Z"}, {"uuid": "23fac5b8-a9d1-4e86-af89-1fddf20a013e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-45810", "type": "seen", "source": "https://t.me/cvedetector/6089", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-45810 - \"Envoy HTTP Async Client Crash Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-45810 \nPublished : Sept. 20, 2024, 12:15 a.m. | 41\u00a0minutes ago \nDescription : Envoy is a cloud-native high-performance edge/middle/service proxy. Envoy will crash when the http async client is handling `sendLocalReply` under some circumstance, e.g., websocket upgrade, and requests mirroring. The http async client will crash during the `sendLocalReply()` in http async client, one reason is http async client is duplicating the status code, another one is the destroy of router is called at the destructor of the async stream, while the stream is deferred deleted at first. There will be problems that the stream decoder is destroyed but its reference is called in `router.onDestroy()`, causing segment fault. This will impact ext_authz if the `upgrade` and `connection` header are allowed, and request mirrorring. This issue has been addressed in versions 1.31.2, 1.30.6, 1.29.9, and 1.28.7. Users are advised to upgrade. There are no known workarounds for this vulnerability. \nSeverity: 6.5 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"20 Sep 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-20T03:01:55.000000Z"}, {"uuid": "2c260490-a4f5-4428-97e1-f7bdf0d01c61", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-45811", "type": "seen", "source": "https://t.me/cvedetector/5850", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-45811 - Vite File Disclosure Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-45811 \nPublished : Sept. 17, 2024, 8:15 p.m. | 41\u00a0minutes ago \nDescription : Vite a frontend build tooling framework for javascript. In affected versions the contents of arbitrary files can be returned to the browser. `@fs` denies access to files outside of Vite serving allow list. Adding `?import&raw` to the URL bypasses this limitation and returns the file content if it exists. This issue has been patched in versions 5.4.6, 5.3.6, 5.2.14, 4.5.5, and 3.2.11. Users are advised to upgrade. There are no known workarounds for this vulnerability. \nSeverity: 4.8 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"17 Sep 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-17T23:08:38.000000Z"}, {"uuid": "50b918ab-d230-4bea-9f65-21ab498f41bb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-45812", "type": "seen", "source": "https://t.me/cvedetector/5847", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-45812 - Vite DOM Clobbering Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-45812 \nPublished : Sept. 17, 2024, 8:15 p.m. | 41\u00a0minutes ago \nDescription : Vite a frontend build tooling framework for javascript. Affected versions of vite were discovered to contain a DOM Clobbering vulnerability when building scripts to `cjs`/`iife`/`umd` output format. The DOM Clobbering gadget in the module can lead to cross-site scripting (XSS) in web pages where scriptless attacker-controlled HTML elements (e.g., an img tag with an unsanitized name attribute) are present. DOM Clobbering is a type of code-reuse attack where the attacker first embeds a piece of non-script, seemingly benign HTML markups in the webpage (e.g. through a post or comment) and leverages the gadgets (pieces of js code) living in the existing javascript code to transform it into executable code. We have identified a DOM Clobbering vulnerability in Vite bundled scripts, particularly when the scripts dynamically import other scripts from the assets folder and the developer sets the build output format to `cjs`, `iife`, or `umd`. In such cases, Vite replaces relative paths starting with `__VITE_ASSET__` using the URL retrieved from `document.currentScript`. However, this implementation is vulnerable to a DOM Clobbering attack. The `document.currentScript` lookup can be shadowed by an attacker via the browser's named DOM tree element access mechanism. This manipulation allows an attacker to replace the intended script element with a malicious HTML element. When this happens, the src attribute of the attacker-controlled element is used as the URL for importing scripts, potentially leading to the dynamic loading of scripts from an attacker-controlled server. This vulnerability can result in cross-site scripting (XSS) attacks on websites that include Vite-bundled files (configured with an output format of `cjs`, `iife`, or `umd`) and allow users to inject certain scriptless HTML tags without properly sanitizing the name or id attributes. This issue has been patched in versions 5.4.6, 5.3.6, 5.2.14, 4.5.5, and 3.2.11. Users are advised to upgrade. There are no known workarounds for this vulnerability. \nSeverity: 6.4 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"17 Sep 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-17T23:08:32.000000Z"}, {"uuid": "e34c47b8-4f26-475a-a83d-98302e4e5c61", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-45816", "type": "seen", "source": "https://t.me/cvedetector/5860", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-45816 - Backstage AWS S3/GCS Bucket Access Bypass Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-45816 \nPublished : Sept. 17, 2024, 9:15 p.m. | 33\u00a0minutes ago \nDescription : Backstage is an open framework for building developer portals. When using the AWS S3 or GCS storage provider for TechDocs it is possible to access content in the entire storage bucket. This can leak contents of the bucket that are not intended to be accessible, as well as bypass permission checks in Backstage. This has been fixed in the 1.10.13 release of the `@backstage/plugin-techdocs-backend` package. All users are advised to upgrade. There are no known workarounds for this vulnerability. \nSeverity: 6.5 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"17 Sep 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-17T23:58:55.000000Z"}, {"uuid": "77292cb4-172e-4918-a9d9-1dfe5334a24a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-45815", "type": "seen", "source": "https://t.me/cvedetector/5859", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-45815 - Backstage Catalog API Query Injection Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-45815 \nPublished : Sept. 17, 2024, 9:15 p.m. | 33\u00a0minutes ago \nDescription : Backstage is an open framework for building developer portals. A malicious actor with authenticated access to a Backstage instance with the catalog backend plugin installed is able to interrupt the service using a specially crafted query to the catalog API. This has been fixed in the `1.26.0` release of the `@backstage/plugin-catalog-backend`. All users are advised to upgrade. There are no known workarounds for this vulnerability. \nSeverity: 6.5 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"17 Sep 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-17T23:58:55.000000Z"}, {"uuid": "89953bb2-ddf2-46f9-b83b-a86840cdbd8e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-45813", "type": "seen", "source": "https://t.me/cvedetector/6001", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-45813 - Find-my-way Regular Expression DOSS Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-45813 \nPublished : Sept. 18, 2024, 5:15 p.m. | 40\u00a0minutes ago \nDescription : find-my-way is a fast, open source HTTP router, internally using a Radix Tree (aka compact Prefix Tree), supports route params, wildcards, and it's framework independent. A bad regular expression is generated any time one has two parameters within a single segment, when adding a `-` at the end, like `/:a-:b-`. This may cause a denial of service in some instances. Users are advised to update to find-my-way v8.2.2 or v9.0.1. or subsequent versions. There are no known workarounds for this issue. \nSeverity: 5.3 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"18 Sep 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-18T20:05:49.000000Z"}]}