Project

General

Profile

Actions
Copy link

Bug #91553

closed

Risk of non-unique field in DatePickerViewHelper

Added by Tizian Schmidlin almost 4 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Form Framework
Target version:
11.0
Start date:
2020-06-02
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
11
PHP Version:
Tags:
Complexity:
no-brainer
Is Regression:
Sprint Focus:

Description

Hello there,

I've discovered an issue with the DatePickerViewHelper.

The method to calculate the field id when rendering the datepicker uses this method to do so:
$id = 'field' . md5(uniqid());

This has some downsides since PHP on Windows does not use microseconds to create the uniqid by default. Therefore the second parameter to uniqid has to be set to ensure its uniqueness.

This bug can be traced back to very old versions of TYPO3.

Best Regards
Tizian

Related issues 3 (0 open — 3 closed)

Related to TYPO3 Core - Task #69730: Remove dot in uniqid('NEW', TRUE)ClosedNicole Cordes2015-09-12

Actions
Related to TYPO3 Core - Bug #58602: Datepicker issue on multiple datetime fields in BEClosed2014-05-07

Actions
Related to TYPO3 Core - Bug #59701: uniqid() not returning unique valuesClosedTymoteusz Motylewski2014-06-20

Actions
Actions
Copy link

Also available in: Atom PDF