On this page
CWE-836: Use of Password Hash Instead of Password for Authentication
Weakness Summary
The product records password hashes in a data store, receives a hash of a password from a client, and compares the supplied hash to the hash obtained from the data store.
- Canonical source: MITRE CWE-836 (opens in a new tab)
- Published Atomicorp CVE observations: 1
- Distinct affected products in those observations: 1
- Active Atomicorp rules associated with this weakness: 10
Atomicorp Research Context
Atomicorp has published CVE-specific research observations associated with this weakness category. Each linked CVE page states whether the tested request was detected or blocked and is the authoritative customer-facing finding.
The CVEs and rules shown here are selected published examples, not a complete list of Atomicorp protections. If a CWE, CVE, or rule is absent from this page, no conclusion should be drawn about whether Atomicorp protects against that weakness or attack method.
A CWE describes a class of software weakness. It does not identify one exploit request, and association with a CWE does not mean that every vulnerability or exploitation path in that category is detected or blocked.
Selected Published CVE Observations
| CVE | Vulnerability | Product | Atomicorp finding | Observed rules |
|---|---|---|---|---|
| CVE-2023-34132 | Sonicwall | analytics | Protected by Atomicorp rules | 340017 , 344361 , 344362 , 344363 , 344364 , 344365 , 344366 , 360148 , 380123 , 393655 |
Associated Atomicorp WAF Rules
| Rule | Status | Behavior |
|---|---|---|
| 340017 | Active | disruptive (deny) |
| 344361 | Active | disruptive (deny) |
| 344362 | Active | disruptive (deny) |
| 344363 | Active | disruptive (deny) |
| 344364 | Active | disruptive (deny) |
| 344365 | Active | disruptive (deny) |
| 344366 | Active | disruptive (deny) |
| 360148 | Active | disruptive (deny) |
| 380123 | Active | disruptive (deny) |
| 393655 | Active | disruptive (deny) |
Related MITRE CAPEC Context
MITRE associates this CWE with the following attack-pattern entries. These taxonomy relationships are context, not Atomicorp coverage claims:
CAPEC-644 (opens in a new tab) , CAPEC-652 (opens in a new tab)