|
2022-01-17
| ||
| 17:37 | • Ticket [e9a2715d91] Tcl 8.6.11: Incompatible Tcl_GetRange() status still Open with 4 other changes artifact: 14056728e9 user: jan.nijtmans | |
| 10:35 | Follow-up to [767e070d35]: Tcl_GetRange and Tcl_GetUniChar do not validate index inputs. Now that T... check-in: 147f3b129a user: jan.nijtmans tags: core-8-6-branch | |
|
2020-03-28
| ||
| 17:25 | • Closed ticket [767e070d35]: Tcl_GetRange and Tcl_GetUniChar do not validate index inputs plus 5 other changes artifact: f8b99c7231 user: jan.nijtmans | |
| 17:24 | • Ticket [767e070d35]: 3 changes artifact: ae6a23a99d user: jan.nijtmans | |
|
2020-03-27
| ||
| 20:58 | Fix [767e070d35]: Tcl_GetRange and Tcl_GetUniChar do not validate index inputs. Backported from 8.7 ... check-in: 5b5ff61672 user: jan.nijtmans tags: core-8-6-branch | |
| 10:33 | Fix [767e070d35]: Tcl_GetRange and Tcl_GetUniChar do not validate index inputs Closed-Leaf check-in: 89f3dff179 user: jan.nijtmans tags: bug-767e070d35 | |
| 10:32 | • Ticket [767e070d35] Tcl_GetRange and Tcl_GetUniChar do not validate index inputs status still Open with 3 other changes artifact: 2f7b03bf66 user: jan.nijtmans | |
|
2020-03-13
| ||
| 16:44 | • New ticket [767e070d35]. artifact: f550e8ca21 user: dgp | |
| Ticket UUID: | 767e070d35e89c53c88f7f4d01c30249ea82466 | |||
| Title: | Tcl_GetRange and Tcl_GetUniChar do not validate index inputs | |||
| Type: | Bug | Version: | all | |
| Submitter: | dgp | Created on: | 2020-03-13 16:44:42 | |
| Subsystem: | 10. Objects | Assigned To: | jan.nijtmans | |
| Priority: | 5 Medium | Severity: | Minor | |
| Status: | Closed | Last Modified: | 2020-03-28 17:25:18 | |
| Resolution: | Fixed | Closed By: | jan.nijtmans | |
| Closed on: | 2020-03-28 17:25:18 | |||
| Description: |
Documentation says nothing about it, but the comments in the code note: "The index is assumed to be in the appropriate range." "The first and last indices are assumed to be in the appropriate range." This is a burden on the caller that should at least be documented. Arguably worse, since the check is not done, the operations of the routines are then free to access unrestrained memory, which seems a risk at least. | |||
| User Comments: |
jan.nijtmans added on 2020-03-28 17:24:57:
Fixed in 8.6 (backported from 8.7) | |||