https://vulnerability.circl.lu/sightings/feed 2026-05-11T06:39:42.186713+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/0bc579db-dfaa-4e84-9384-43ac8650eb8e/export 2026-05-11T06:39:42.577886+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "0bc579db-dfaa-4e84-9384-43ac8650eb8e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-48924", "type": "seen", "source": "https://t.me/cvedetector/8256", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-48924 - MessagePack CSharp Hash Collision CPU Consumption Denial of Service Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-48924 \nPublished : Oct. 17, 2024, 9:15 p.m. | 40\u00a0minutes ago \nDescription : ### Impact \n \nWhen this library is used to deserialize messagepack data from an untrusted source, there is a risk of a denial of service attack by an attacker that sends data contrived to produce hash collisions, leading to large CPU consumption disproportionate to the size of the data being deserialized. \n \nThis is similar to [a prior advisory](), which provided an inadequate fix for the hash collision part of the vulnerability. \n \n### Patches \n \nThe following steps are required to mitigate this risk. \n \n1. Upgrade to a version of the library where a fix is available. \n1. Review the steps in [this previous advisory]() to ensure you have your application configured for untrusted data. \n \n### Workarounds \n \nIf upgrading MessagePack to a patched version is not an option for you, you may apply a manual workaround as follows: \n \n1. Declare a class that derives from `MessagePackSecurity`. \n2. Override the `GetHashCollisionResistantEqualityComparer` method to provide a collision-resistant hash function of your own and avoid calling `base.GetHashCollisionResistantEqualityComparer()`. \n3. Configure a `MessagePackSerializerOptions` with an instance of your derived type by calling `WithSecurity` on an existing options object. \n4. Use your custom options object for all deserialization operations. This may be by setting the `MessagePackSerializer.DefaultOptions` static property, if you call methods that rely on this default property, and/or by passing in the options object explicitly to any `Deserialize` method. \n \n### References \n \n- Learn more about best security practices when reading untrusted data with [MessagePack 1.x]() or [MessagePack 2.x](). \n- The .NET team's [discussion on hash collision vulnerabilities of their `HashCode` struct](). \n \n### For more information \n \nIf you have any questions or comments about this advisory: \n \n* [Start a public discussion]() \n* [Email us privately](mailto:andrewarnott@live.com) \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"17 Oct 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-18T00:11:03.000000Z"} 2024-10-18T00:11:03+00:00