View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0003969||Composr||core||public||2019-11-26 20:36||2019-11-26 20:37|
|Reporter||Chris Graham||Assigned To||Chris Graham|
|Fixed in Version||10.0.29|
|Summary||0003969: Better handling of integer boundaries, esp for point charging|
|Description||Point charging/refunding doesn't do a bounds check on the minimum points a user can have. Testing with very-large/very-negative values can cause an overflow.|
This isn't a realistic scenario, but staff shouldn't be able to create stack traces through the UI.
Also comment more cases where we are limiting ourselves to 32 bit signed numbers as being related to 0003046.
|Tags||No tags attached.|
|Time estimation (hours)|
Fixed in git commit 1faafa789 (https://gitlab.com/composr-foundation/composr/commit/1faafa789 - link will become active once code pushed to GitLab)
A hotfix (a TAR of files to upload) have been uploaded to this issue. These files are made to the latest intra-version state (i.e. may roll in earlier fixes too if made to the same files) - so only upload files newer than what you have already. Always take backups of files you are replacing or keep a copy of the manual installer for your version, and only apply fixes you need. These hotfixes are not necessarily reliable or well supported. Not sure how to extract TAR files to your Windows computer? Try 7-zip (http://www.7-zip.org/).
hotfix-3969, 2019-11-26 8pm.tar (327,680 bytes)