{"vulnerability": "CVE-2024-36066", "sightings": [{"uuid": "a5db5c67-9741-424f-859f-731615ae3543", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-36066", "type": "seen", "source": "https://t.me/cvedetector/5517", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-36066 - KeyFactor EJBCA CMP CLI Client Salt Forgery V\u00edrus\", \n  \"Content\": \"CVE ID : CVE-2024-36066 \nPublished : Sept. 12, 2024, 7:15 p.m. | 35\u00a0minutes ago \nDescription : The CMP CLI client in KeyFactor EJBCA before 8.3.1 has only 6 octets of salt, and is thus not compliant with the security requirements of RFC 4211, and might make man-in-the-middle attacks easier. CMP includes password-based MAC as one of the options for message integrity and authentication (the other option is certificate-based). RFC 4211 section 4.4 requires that password-based MAC parameters use a salt with a random value of at least 8 octets. This helps to inhibit dictionary attacks. Because the standalone CMP client originally was developed as test code, the salt was instead hardcoded and only 6 octets long. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"12 Sep 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-12T21:53:38.000000Z"}, {"uuid": "a1a996c7-c362-4322-9bb3-80035a72ba48", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-36066", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/8703", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-36066\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: The CMP CLI client in KeyFactor EJBCA before 8.3.1 has only 6 octets of salt, and is thus not compliant with the security requirements of RFC 4211, and might make man-in-the-middle attacks easier. CMP includes password-based MAC as one of the options for message integrity and authentication (the other option is certificate-based). RFC 4211 section 4.4 requires that password-based MAC parameters use a salt with a random value of at least 8 octets. This helps to inhibit dictionary attacks. Because the standalone CMP client originally was developed as test code, the salt was instead hardcoded and only 6 octets long.\n\ud83d\udccf Published: 2024-09-12T00:00:00.000Z\n\ud83d\udccf Modified: 2025-03-25T16:10:43.486Z\n\ud83d\udd17 References:\n1. https://datatracker.ietf.org/doc/html/rfc4211#section-4.4\n2. https://support.keyfactor.com/hc/en-us/articles/26965687021595-EJBCA-Security-Advisory-EJBCA-standalone-CMP-CLI-client", "creation_timestamp": "2025-03-25T16:25:10.000000Z"}]}