setKey
Defined in 2 files
Last patched
Overview
setKey in igniterealtime/Openfire was changed by 2 published CVE fixes between 2019 and 2023, in 3 distinct patches that added or removed 33 lines in total.
Defined in 2 files
Last patched
setKey in igniterealtime/Openfire was changed by 2 published CVE fixes between 2019 and 2023, in 3 distinct patches that added or removed 33 lines in total.
The name occurs in 2 files: xmppserver/src/main/java/org/jivesoftware/admin/AuthCheckFilter.java, xmppserver/src/main/java/org/jivesoftware/openfire/container/PluginServlet.java.
igniterealtime/Openfire has 14 CVEs with a located fix in total, so 14% of them touched this function.
Every published CVE whose fix changed setKey, newest first, with the lines each fix touched.
CVE-2023-32315 · xmppserver/src/main/java/org/jivesoftware/admin/AuthCheckFilter.java · line 62 · +0 −27
CVE-2019-18393 · xmppserver/src/main/java/org/jivesoftware/openfire/container/PluginServlet.java · lines 81–86 · +6 −0
Get an alert when the next CVE fix lands in igniterealtime/Openfire, with the patched functions.
Monitor Openfire CVEsFunctions in the same files that CVE fixes also changed.
Functions in igniterealtime/Openfire changed by the most CVE fixes.
Common questions about CVE fixes to setKey.
Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.
Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.