In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsLearn about Insufficient Session Expiration vulnerabilities in an interactive lesson.
Start learningThere is no fixed version for Debian:12
kanboard
.
Note: Versions mentioned in the description apply only to the upstream kanboard
package and not the kanboard
package as distributed by Debian
.
See How to fix?
for Debian:12
relevant fixed versions and status.
Kanboard is project management software that focuses on the Kanban methodology. In affected versions sessions are still usable even though their lifetime has exceeded. Kanboard implements a cutom session handler (app/Core/Session/SessionHandler.php
), to store the session data in a database. Therefore, when a session_id
is given, kanboard queries the data from the sessions
sql table. At this point, it does not correctly verify, if a given session_id
has already exceeded its lifetime (expires_at
).
Thus, a session which's lifetime is already > time()
, is still queried from the database and hence a valid login. The implemented SessionHandlerInterface::gc function, that does remove invalid sessions, is called only with a certain probability (Cleans up expired sessions. Called by session_start()
, based on session.gc_divisor
, session.gc_probability
and session.gc_maxlifetime
settings) accordingly to the php documentation. In the official Kanboard docker image these values default to: session.gc_probability=1, session.gc_divisor=1000. Thus, an expired session is only terminated with probability 1/1000. This issue has been addressed in release 1.2.43 and all users are advised to upgrade. There are no known workarounds for this vulnerability.