37 matches found
CVE-2025-62819
Keyfactor EJBCA through 9.3.3 performs insufficient authorization checks when self-renewing a client certificate via the RA Registration Authority User Interface. This allows a remote user, authenticated with a valid client certificate, to renew their certificate even if the end entity status...
Keyfactor EJBCA security vulnerability
Keyfactor EJBCA versions 9.3.3 and earlier contain a security vulnerability. This vulnerability stems from insufficient authorization checks when self-signing client certificates via the RA Registration Authority user interface. A remote attacker who possesses a valid TLS client certificate and...
CVE-2025-62819
Keyfactor EJBCA versions through 9.3.3 are vulnerable to insufficient authorization checks during the self-renewal of client certificates via the RA (Registration Authority) User Interface . A remote user with a valid TLS client certificate—and authorization to use the RA User Interface either th...
EUVD-2025-211240
Keyfactor EJBCA through 9.3.3 performs insufficient authorization checks when self-renewing a client certificate via the RA Registration Authority User Interface. This allows a remote user, authenticated with a valid client certificate, to renew their certificate even if the end entity status...
CVE-2025-62819
Keyfactor EJBCA through 9.3.3 performs insufficient authorization checks when self-renewing a client certificate via the RA Registration Authority User Interface. This allows a remote user, authenticated with a valid client certificate, to renew their certificate even if the end entity status...
PT-2026-135437
Keyfactor EJBCA through 9.3.3 performs insufficient authorization checks when self-renewing a client certificate via the RA Registration Authority User Interface. This allows a remote user, authenticated with a valid client certificate, to renew their certificate even if the end entity status...
CVE-2025-62819: n/a: Keyfactor EJBCA through 9.3.3 performs insufficient authorization checks when self-renewing a client certificate via…
Keyfactor EJBCA through 9.3.3 performs insufficient authorization checks when self-renewing a client certificate via the RA Registration Authority User Interface. This allows a remote user, authenticated with a valid client certificate, to renew their certificate even if the end entity status...
CVE-2025-49602
An issue was discovered in Keyfactor EJBCA 9. When an administrator is removed from its administrator role while having a valid TLS session, EJBCA may, in certain circumstances, cache authentication for longer than the configured maximum time default: 30 seconds, which results in the former...
PT-2026-133669
Name of the Vulnerable Software and Affected Versions Keyfactor EJBCA version 9 Description An issue exists where authentication may be cached longer than the configured maximum time default 30 seconds when an administrator is removed from their role while maintaining a valid TLS session. This...
EUVD-2025-211227
An issue was discovered in Keyfactor EJBCA 9. When an administrator is removed from its administrator role while having a valid TLS session, EJBCA may, in certain circumstances, cache authentication for longer than the configured maximum time default: 30 seconds, which results in the former...
CVE-2025-49602
An issue was discovered in Keyfactor EJBCA 9. When an administrator is removed from its administrator role while having a valid TLS session, EJBCA may, in certain circumstances, cache authentication for longer than the configured maximum time default: 30 seconds, which results in the former...
CVE-2025-49602: n/a: An issue was discovered in Keyfactor EJBCA 9
An issue was discovered in Keyfactor EJBCA 9. When an administrator is removed from its administrator role while having a valid TLS session, EJBCA may, in certain circumstances, cache authentication for longer than the configured maximum time default: 30 seconds, which results in the former...
CVE-2025-49602
An authentication caching issue exists in Keyfactor EJBCA 9 . If an administrator is removed from their role while maintaining an active TLS session , the system may cache their authentication for longer than the configured maximum time (default is 30 seconds ). This allows the former administrat...
CVE-2022-42954
Keyfactor EJBCA before 7.10.0 allows XSS...
EUVD-2022-46009
Malicious code in bioql PyPI...
EUVD-2023-38295
Malicious code in bioql PyPI...
CVE-2024-36066
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...
CVE-2023-34196
In the Keyfactor EJBCA before 8.0.0, the RA web certificate distribution servlet /ejbca/ra/cert allows partial denial of service due to an authentication issue. In configurations using OAuth, disclosure of CA certificates attributes and public keys to unauthenticated or less privileged users may...
CVE-2022-34831
An issue was discovered in Keyfactor PrimeKey EJBCA before 7.9.0, related to possible inconsistencies in DNS identifiers submitted in an ACME order and the corresponding CSR submitted during finalization. During the ACME enrollment process, an order is submitted containing an identifier for one o...
CVE-2024-36066
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...