Issue Bug Closed

#19867DB session records are only created when users authenticate

Marcus Krause 01/20/09, 22:40 updated 10/02/18, 12:26

Description

Functions $GLOBALS[“TSFE”]->fe_user->getKey() or $GLOBALS[“TSFE”]->fe_user->setKey() allow to bind data to a user’s session.
Unfortunately TYPO3 only creates DB session records in tables be_sessions/fe_sessions if a user authenticates.

Before applying the session fixation fix, TYPO3 always trusted the session id provided by the user through COOKIE etc. Although no DB session records were created, setKey() and getKey() worked in a way that a record in fe_session_data was created (including session id) and could be accessed.

Now, after the session fixation fix, TYPO3 will issue a new session id if there’s no according db record in be_sessions/fe_sessions. This now has the drawback that every request of a non-authenticated user will force TYPO3 to issue a new session id so that getKey() no longer works as existing records in fe_session_data are associated to an “old” session identifier.

I believe that the security fix is not the cause of the problem but the trigger for it. I expect TYPO3 to create a DB session record whenever a session id is generated not only when a user authenticates itself.

(issue imported from #M10205)

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.