https://vulnerability.circl.lu/sightings/feed 2026-06-22T10:50:43.565969+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/d5971b98-8b59-4faa-a852-7d4193e4d881/export 2026-06-22T10:50:43.958614+00:00 Automation user https://cvepremium.circl.lu/user/automation {"uuid": "d5971b98-8b59-4faa-a852-7d4193e4d881", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-28942", "type": "seen", "source": "https://t.me/cibsecurity/16601", "content": "\u203c CVE-2020-28942 \u203c\n\nAn issue exists in PrimeKey EJBCA before 7.4.3 when enrolling with EST while proxied through an RA over the Peers protocol. As a part of EJBCA's domain security model, the peer connector allows the restriction of client certificates (for the RA, not the end user) to a limited set of allowed CAs, thus restricting the accessibility of that RA to the rights it has within a specific role. While this works for other protocols such as CMP, it was found that the EJBCA enrollment over an EST implementation bypasses this check, allowing enrollment with a valid client certificate through any functioning and authenticated RA connected to the CA. NOTE: an attacker must already have a trusted client certificate and authorization to enroll against the targeted CA.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2020-11-19T20:41:39.000000Z"} 2020-11-19T20:41:39+00:00