On this page
CWE-310: Common Weakness Enumeration category
Weakness Summary
- Canonical source: MITRE CWE-310 (opens in a new tab)
- Published Atomicorp CVE observations: 2
- Distinct affected products in those observations: 1
- Active Atomicorp rules associated with this weakness: 1
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-2014-0866 | IBM Algorithmics RICOS 4.5.0 < 4.7.0 - Multiple Vulnerabilities | algo credit limits | Attack Blocked by Atomicorp | 392301 |
| CVE-2014-0869 | IBM Algorithmics RICOS 4.5.0 < 4.7.0 - Multiple Vulnerabilities | algo credit limits | Attack Blocked by Atomicorp | 392301 |
Associated Atomicorp WAF Rules
| Rule | Status | Behavior |
|---|---|---|
| 392301 | Active | disruptive (deny) |