On this page
CWE-326: Inadequate Encryption Strength
Weakness Summary
The product stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required.
- Canonical source: MITRE CWE-326 (opens in a new tab)
- Published Atomicorp CVE observations: 2
- Distinct affected products in those observations: 1
- Active Atomicorp rules associated with this weakness: 2
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-2018-15811 | DotNetNuke 9.2 - 9.2.1 - Weak Encryption & Cookie Deserialization | dotnetnuke | Attack Blocked by Atomicorp | 344365 , 344370 |
| CVE-2018-18325 | DotNetNuke 9.2 - 9.2.2 - Weak Encryption & Cookie Deserialization | dotnetnuke | Attack Blocked by Atomicorp | 344365 , 344370 |
Associated Atomicorp WAF Rules
| Rule | Status | Behavior |
|---|---|---|
| 344365 | Active | disruptive (deny) |
| 344370 | 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-112 (opens in a new tab) , CAPEC-192 (opens in a new tab) , CAPEC-20 (opens in a new tab)