Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CWE-760 (使用可预测Salt的单向哈希算法) — Vulnerability Class 5

5 vulnerabilities classified as CWE-760 (使用可预测Salt的单向哈希算法). AI Chinese analysis included.

CWE-760 represents a cryptographic weakness where developers use a one-way hash function with a predictable or static salt for sensitive data like passwords. This flaw undermines security because attackers can easily pre-compute hash values using dictionary attacks or rainbow tables, effectively bypassing the protective barrier that an unpredictable salt is meant to provide. By knowing the salt in advance, adversaries can reverse-engineer common passwords without needing to crack individual hashes during an attack. To mitigate this risk, developers must generate a unique, cryptographically secure random salt for every user account. This salt should be stored alongside the hashed password, ensuring that even identical passwords result in distinct hash outputs, thereby neutralizing pre-computation attacks and significantly increasing the computational cost required for brute-force efforts.

MITRE CWE Description
The product uses a one-way cryptographic hash against an input that should not be reversible, such as a password, but the product uses a predictable salt as part of the input. This makes it easier for attackers to pre-compute the hash value using dictionary attack techniques such as rainbow tables, effectively disabling the protection that an unpredictable salt would provide. It should be noted that, despite common perceptions, the use of a good salt with a hash does not sufficiently increase the effort for an attacker who is targeting an individual password, or who has a large amount of computing resources available, such as with cloud-based services or specialized, inexpensive hardware. Offline password cracking can still be effective if the hash function is not expensive to compute; many cryptographic functions are designed to be efficient and can be vulnerable to attacks using massive computing resources, even if the hash is cryptographically strong. The use of a salt only slightly increases the computing requirements for an attacker compared to other strategies such as adaptive hash functions. See CWE-916 for more details.
Common Consequences (1)
Access ControlBypass Protection Mechanism
Mitigations (2)
Architecture and DesignUse an adaptive hash function that can be configured to change the amount of computational effort needed to compute the hash, such as the number of iterations ("stretching") or the amount of memory required. Some hash functions perform salting automatically. These functions can significantly increase the overhead for a brute force attack compared to intentionally-fast functions such as MD5. For ex…
Effectiveness: High
ImplementationIf a technique that requires extra computational effort can not be implemented, then for each password that is processed, generate a new random salt using a strong random number generator with unpredictable seeds. Add the salt to the plaintext password before hashing it. When storing the hash, also store the salt. Do not use the same salt for every password.
Effectiveness: Limited
CVE IDTitleCVSSSeverityPublished
CVE-2025-9290 Authentication Weakness on Omada Controllers, Gateways and Access Points — Omada Software Controller 5.9 -2026-01-22
CVE-2024-13951 One way hash with predictable salt — ASPECT-Enterprise 7.6 High2025-05-22
CVE-2023-22599 InHand Networks InRouter302 安全漏洞 — InRouter 302 7.0 High2023-01-12
CVE-2020-28214 Schneider Electric Modicon M221 安全漏洞 — Modicon M221 (all references, all versions) 5.5 -2020-12-11
CVE-2018-5552 DocuTrac DTISQLInstaller.exe Hard-Coded Salt — DTISQLInstaller.exe 7.5 -2018-03-19

Vulnerabilities classified as CWE-760 (使用可预测Salt的单向哈希算法) represent 5 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.