An issue was discovered in Keyfactor EJBCA 9.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Keyfactor EJBCA, an open-source public key infrastructure (PKI) and certificate authority software, is affected by this vulnerability. A former administrator whose role was removed may keep access to the system for longer than intended, because authentication is cached past the configured time limit during an active TLS session.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
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 administrator retaining access that they should no longer have.
Timeline
- CVE published
- Record last updated
- First seen by cve.now
Affected versions
No affected packages have been listed by the sources.