Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: V2.0.8.0, V2.0.8.3, V2.0.8.4, V2.0.8.5, V2.0.8.7, V2.0.8.8, V2.0.8.9, V2.0.8.10, V2.0.8.11, V2.0.8.12, V2.0.8.14, V2.0.8.15, V2.0.8.16, V2.0.8.17, V2.0.8.18, V2.0.8.19, V2.0.8.20, V2.0.8.21, V2.0.8.22, V2.0.8.23, V2.0.8.24, V2.0.8.25, V2.1.1.0, V2.1.2.0, V2.1.3.0, V2.1.4.0, V2.1.5.0, V2.1.5.1, V2.1.6.0, V2.1.6.1, V2.1.7.0, V2.1.7.1, V2.1.8.0, V2.1.8.1, V2.1.9.0, V2.1.9.1, V2.1.10.0
-
Component/s: Middleware
-
Labels:None
-
Account:SDO rcX (SDORCX)
Description
Currently any MidFAT file operation takes the special entries "." (single dot) and ".." (double dot) as valid input path. The file operations listed below should refuse those special entries as the operation is not reasonable or even compromise file system integrity:
- Mid_FatCreateFile
- Mid_FatOpenFile
- Mid_FatRename
- Mid_FatDelete
- Mid_FatMakeDirectory
Implementation of initial request is refused:
if Mid_FatDelete(hVol,".") is called on an empty directory, rcx delete the entry and free the sectors in the FAT.
In the Parent directory the link to this directory is not removed.
A later write to this directory will overwrite data which is may stored to this location.