Unsafe standard encryption function
Function is not reentrant or uses a risky encryption algorithm
Description
This defect occurs when a standard encryption function uses a broken or weak cryptographic
algorithm. For example, crypt
is not reentrant and is based on the
risky Data Encryption Standard (DES).
Risk
The use of a broken, weak, or nonstandard algorithm can expose sensitive information to an attacker. A determined hacker can access the protected data using various techniques.
If the weak function is nonreentrant, when you use the function in concurrent programs, there is an additional race condition risk.
Fix
Avoid functions that use these encryption algorithms. Instead, use a reentrant function that uses a stronger encryption algorithm.
Note
Some implementations of crypt
support additional,
possibly more secure, encryption algorithms.
Examples
Result Information
Group: Security |
Language: C | C++ |
Default: Off |
Command-Line Syntax: UNSAFE_STD_CRYPT |
Impact: Medium |
Version History
Introduced in R2015b
See Also
Deterministic random output from constant seed
| Predictable random output from predictable seed
| Vulnerable pseudo-random number generator
| Find defects (-checkers)
Topics
- Interpret Bug Finder Results in Polyspace Desktop User Interface
- Interpret Bug Finder Results in Polyspace Access Web Interface (Polyspace Access)
- Address Results in Polyspace User Interface Through Bug Fixes or Justifications
- Address Results in Polyspace Access Through Bug Fixes or Justifications (Polyspace Access)