Potentially unsafe usage of `Arc::get_mut`RS-S1000
In the standard library in Rust before 1.29.0, there is weak synchronization in the
Arc::get_mut method. This synchronization issue can be lead to memory safety issues
through race conditions.
Potentially unsafe usage of `std::fs::remove_dir_all`RS-S1002
In the standard library in Rust before 1.58.1, there is a race condition that enables symlink following. An attacker could take advantage of this security vulnerability to trick a privileged program into deleting files and directories the attacker couldn't otherwise access or delete.
Hardcoded temporary file or directory detectedRS-S1003
This issue is raised when a hardcoded temporary file or directory is detected. Creating and using insecure temporary files can leave the application vulnerable to attacks. Lack of uniqueness in temporary files allows attackers to predict the filename and inject dangerous data into the application through the temporary file.
Insufficient RSA key sizeRS-S1005
The strength of public-key-based cryptographic algorithm (like RSA) is determined by the time that it takes to derive the private key by using brute-force methods. 1024-bit keys are to be avoided since they are easy to brute-force. However, 2048-bit keys are said to be sufficient until 2030. Preferably use 4096-bit keys.
Detected invisible unicode characterRS-S1010
The presence of invisible Unicode characters can lead to various vulnerabilities that may be hard to detect with a simple code review. Consider revisiting this line of code.