--- Comment #2 from Jason Shepherd <jshepherd(a)redhat.com> ---
From upstream advisory:
As of publication of this advisory, we are aware of the following potential
attacks in the latest Jenkins releases that do not yet contain this fix:
Unauthenticated users can invalidate all sessions
Users with Overall/Read permission could create new user objects in memory.
Users with Overall/Read access could manually kick off otherwise periodically
executed runs of implementations of AsyncPeriodicWork.
Given the vast potential attack surface, we fully expect other attacks, that we
are not currently aware of, to be possible on Jenkins releases that do not have
this fix applied. This is reflected in the high score we assigned to this
issue, rather than limiting the score to the impact through known issues.
You are receiving this mail because:
You are on the CC list for the bug.