{"vulnerability": "CVE-2024-4976", "sightings": [{"uuid": "deee77e8-74b9-4725-bf51-700a1095cb4c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-49765", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3ldoosffasn2a", "content": "", "creation_timestamp": "2024-12-19T20:15:25.569908Z"}, {"uuid": "67414059-ec26-4ac4-8a8c-7eb6d5686f7c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-49765", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113681106505075065", "content": "", "creation_timestamp": "2024-12-19T19:20:25.010276Z"}, {"uuid": "00bd729d-a976-4d55-be5b-d8657957f96f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-49765", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113681119402600838", "content": "", "creation_timestamp": "2024-12-19T19:23:41.850610Z"}, {"uuid": "fd597bf3-78b5-444f-8671-4025199ce16e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-49761", "type": "seen", "source": "https://gist.github.com/junaruga/54659f7454f91314cafc3fd341b36b39", "content": "", "creation_timestamp": "2025-03-17T15:53:47.000000Z"}, {"uuid": "902ce594-61f1-4610-b149-df90cc8d2e62", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-49761", "type": "seen", "source": "https://gist.github.com/junaruga/f1ad603ec98ddc5c21f2ab6fa21c121d", "content": "", "creation_timestamp": "2025-03-27T14:13:15.000000Z"}, {"uuid": "a5834b4b-5107-4145-b5df-53e6e17efb87", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-49766", "type": "seen", "source": "MISP/af790da0-9e28-4cb7-bd4e-46ad005115c6", "content": "", "creation_timestamp": "2025-10-01T18:11:57.000000Z"}, {"uuid": "529f1ef5-d8f3-40d6-949a-2259a6b0c057", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-49766", "type": "seen", "source": "MISP/af790da0-9e28-4cb7-bd4e-46ad005115c6", "content": "", "creation_timestamp": "2025-10-08T21:59:32.000000Z"}, {"uuid": "30f031e1-2cd6-4c83-aff7-eb380c0a2e1c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-49763", "type": "seen", "source": "https://t.me/cvedetector/11807", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-49763 - PlexRipper Open CORS Policy Information Disclosure\", \n  \"Content\": \"CVE ID : CVE-2024-49763 \nPublished : Dec. 2, 2024, 5:15 p.m. | 51\u00a0minutes ago \nDescription : PlexRipper is a cross-platform media downloader for Plex. PlexRipper\u2019s open CORS policy allows attackers to gain sensitive information from PlexRipper by getting the user to access the attacker\u2019s domain. This allows an attacking website to access the /api/PlexAccount endpoint and steal the user\u2019s Plex login. This vulnerability is fixed in 0.24.0. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"02 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-02T19:35:52.000000Z"}, {"uuid": "dfef7aa4-2eb2-465a-ba05-5a0dfea11b0e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-49765", "type": "seen", "source": "https://t.me/cvedetector/13366", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-49765 - Discourse Local Login Bypass Authentication Weakness\", \n  \"Content\": \"CVE ID : CVE-2024-49765 \nPublished : Dec. 19, 2024, 8:15 p.m. | 41\u00a0minutes ago \nDescription : Discourse is an open source platform for community discussion. Sites that are using discourse connect but still have local logins enabled could allow attackers to bypass discourse connect to create accounts and login. This problem is patched in the latest version of Discourse. Users unable to upgrade who are using discourse connect may disable all other login methods as a workaround. \nSeverity: 5.3 | MEDIUM \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-19T22:20:48.000000Z"}, {"uuid": "69f5a342-64a5-4329-8659-ad09732ab7fa", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-49764", "type": "seen", "source": "https://t.me/cvedetector/11108", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-49764 - LibreNMS Stored Cross-Site Scripting (XSS)\", \n  \"Content\": \"CVE ID : CVE-2024-49764 \nPublished : Nov. 15, 2024, 4:15 p.m. | 44\u00a0minutes ago \nDescription : LibreNMS is an open-source, PHP/MySQL/SNMP-based network monitoring system. A Stored Cross-Site Scripting (XSS) vulnerability in the \"Capture Debug Information\" page allows authenticated users to inject arbitrary JavaScript through the \"hostname\" parameter when creating a new device. This vulnerability results in the execution of malicious code when the \"Capture Debug Information\" page is visited, redirecting the user and sending non-httponly cookies to an attacker-controlled domain. This vulnerability is fixed in 24.10.0. \nSeverity: 4.8 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"15 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-15T18:17:27.000000Z"}, {"uuid": "0edfeef2-9dda-46a5-ab55-78cdd1564dbd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-49766", "type": "seen", "source": "https://t.me/cvedetector/8981", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-49766 - Werkzeug Windows UNC Path Disclosure Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-49766 \nPublished : Oct. 25, 2024, 8:15 p.m. | 31\u00a0minutes ago \nDescription : Werkzeug is a Web Server Gateway Interface web application library. On Python < 3.11 on Windows, os.path.isabs() does not catch UNC paths like //server/share. Werkzeug's safe_join() relies on this check, and so can produce a path that is not safe, potentially allowing unintended access to data. Applications using Python >= 3.11, or not using Windows, are not vulnerable. Werkzeug version 3.0.6 contains a patch. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"25 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-25T22:56:22.000000Z"}, {"uuid": "c2f45b3a-47fb-45c8-b8af-45aee99b2056", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-49768", "type": "seen", "source": "https://t.me/cvedetector/9339", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-49768 - Waitress HTTP Pipelining Request Hijacking Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-49768 \nPublished : Oct. 29, 2024, 3:15 p.m. | 43\u00a0minutes ago \nDescription : Waitress is a Web Server Gateway Interface server for Python 2 and 3. A remote client may send a request that is exactly recv_bytes (defaults to 8192) long, followed by a secondary request using HTTP pipelining. When request lookahead is disabled (default) we won't read any more requests, and when the first request fails due to a parsing error, we simply close the connection. However when request lookahead is enabled, it is possible to process and receive the first request, start sending the error message back to the client while we read the next request and queue it. This will allow the secondary request to be serviced by the worker thread while the connection should be closed. Waitress 3.0.1 fixes the race condition. As a workaround, disable channel_request_lookahead, this is set to 0 by default disabling this feature. \nSeverity: 9.1 | CRITICAL \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-29T17:17:23.000000Z"}, {"uuid": "23ab6840-f506-4fe9-97c9-35c00b83df4c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-49769", "type": "seen", "source": "https://t.me/cvedetector/9338", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-49769 - Waitress DoS Lockup Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-49769 \nPublished : Oct. 29, 2024, 3:15 p.m. | 43\u00a0minutes ago \nDescription : Waitress is a Web Server Gateway Interface server for Python 2 and 3. When a remote client closes the connection before waitress has had the opportunity to call getpeername() waitress won't correctly clean up the connection leading to the main thread attempting to write to a socket that no longer exists, but not removing it from the list of sockets to attempt to process. This leads to a busy-loop calling the write function. A remote attacker could run waitress out of available sockets with very little resources required. Waitress 3.0.1 contains fixes that remove the race condition. \nSeverity: 7.5 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-29T17:17:22.000000Z"}, {"uuid": "949817e9-fa19-45c6-a05d-5b5712f1e9b2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-49761", "type": "seen", "source": "https://t.me/cvedetector/9131", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-49761 - \"REXML XML Toolkit ReDoS Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-49761 \nPublished : Oct. 28, 2024, 3:15 p.m. | 44\u00a0minutes ago \nDescription : REXML is an XML toolkit for Ruby. The REXML gem before 3.3.9 has a ReDoS vulnerability when it parses an XML that has many digits between  and x...; in a hex numeric character reference (...;). This does not happen with Ruby 3.2 or later. Ruby 3.1 is the only affected maintained Ruby. The REXML gem 3.3.9 or later include the patch to fix the vulnerability. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"28 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-28T17:00:07.000000Z"}, {"uuid": "85ac51e7-cb05-4630-bae6-5b9f31525aec", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-49760", "type": "seen", "source": "https://t.me/cvedetector/8868", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-49760 - OpenRefine File System Path Traversal Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-49760 \nPublished : Oct. 24, 2024, 10:15 p.m. | 36\u00a0minutes ago \nDescription : OpenRefine is a free, open source tool for working with messy data. The load-language command expects a `lang` parameter from which it constructs the path of the localization file to load, of the form `translations-$LANG.json`. But when doing so in versions prior to 3.8.3, it does not check that the resulting path is in the expected directory, which means that this command could be exploited to read other JSON files on the file system. Version 3.8.3 addresses this issue. \nSeverity: 7.1 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"25 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-25T01:11:55.000000Z"}, {"uuid": "cb7982da-79a7-4367-b7a3-e2970d8159d3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-49767", "type": "seen", "source": "https://t.me/cvedetector/8980", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-49767 - Flask Werkzeug Multipart Form Data Denial of Service Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-49767 \nPublished : Oct. 25, 2024, 8:15 p.m. | 31\u00a0minutes ago \nDescription : Werkzeug is a Web Server Gateway Interface web application library. Applications using `werkzeug.formparser.MultiPartParser` corresponding to a version of Werkzeug prior to 3.0.6 to parse `multipart/form-data` requests (e.g. all flask applications) are vulnerable to a relatively simple but effective resource exhaustion (denial of service) attack. A specifically crafted form submission request can cause the parser to allocate and block 3 to 8 times the upload size in main memory. There is no upper limit; a single upload at 1 Gbit/s can exhaust 32 GB of RAM in less than 60 seconds. Werkzeug version 3.0.6 fixes this issue. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"25 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-25T22:56:21.000000Z"}, {"uuid": "e1dd6934-9841-4d39-92f8-35d131ace1aa", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-49762", "type": "seen", "source": "https://t.me/cvedetector/8871", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-49762 - Pterodactyl 2FA Password Disclosure Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-49762 \nPublished : Oct. 24, 2024, 10:15 p.m. | 36\u00a0minutes ago \nDescription : Pterodactyl is a free, open-source game server management panel. When a user disables two-factor authentication via the Panel, a `DELETE` request with their current password in a query parameter will be sent.  While query parameters are encrypted when using TLS, many webservers (including ones officially documented for use with Pterodactyl) will log query parameters in plain-text, storing a user's password in plain text. Prior to version 1.11.8, if a malicious user obtains access to these logs they could potentially authenticate against a user's account; assuming they are able to discover the account's email address or username separately. This problem has been patched in version 1.11.8. There are no workarounds at this time. There is not a direct vulnerability within the software as it relates to logs generated by intermediate components such as web servers or Layer 7 proxies. Updating to `v1.11.8` or adding the linked patch manually are the only ways to avoid this problem. As this vulnerability relates to historical logging of sensitive data, users who have ever disabled 2FA on a Panel (self-hosted or operated by a company) should change their passwords and consider enabling 2FA if it was left disabled. While it's unlikely that their account swill be compromised by this vulnerability, it's not impossible. Panel administrators should consider clearing any access logs that may contain sensitive data. \nSeverity: 4.6 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"25 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-25T01:11:57.000000Z"}]}