CWE-1118: Insufficient Documentation of Error Handling Techniques
The documentation does not sufficiently describe the techniques that are used for error handling, exception processing, or similar mechanisms.
Last updated
Overview
Documentation may need to cover error handling techniques at multiple layers, such as module, executable, compilable code unit, or callable.
Real-world CVEs
1 recorded CVEs are caused by CWE-1118 (Insufficient Documentation of Error Handling Techniques). The highest-severity and most recent are shown first.
Common consequences
What can happen when CWE-1118 is exploited.
Reduce Maintainability
Affects: Other
How it happens
When it is introduced
Typically introduced during these phases of the software lifecycle.
Frequently asked questions
Common questions about CWE-1118.
- What is CWE-1118?
- The documentation does not sufficiently describe the techniques that are used for error handling, exception processing, or similar mechanisms.
- What CVEs are caused by CWE-1118?
- 1 recorded CVEs are attributed to CWE-1118, including CVE-2022-1459.
- What are the consequences of CWE-1118?
- Exploiting CWE-1118 can lead to: Reduce Maintainability.
- Is CWE-1118 actively exploited?
- 1 recorded CVEs are caused by CWE-1118; none are currently in CISA's KEV catalog of actively exploited flaws.
References
- MITRE CWE definition (CWE-1118) (opens in a new tab)
- CWE-1118 vulnerabilities on NVD (opens in a new tab)
- Learn: What is a CWE?
Weakness data is sourced from the MITRE CWE catalog (v4.20). CVE associations are aggregated and kept current by RadicalNotion.AI.
Stay ahead of CWE-1118
Get alerted the moment a new CWE-1118 vulnerability affects your stack, with AI-written analysis, severity context, and remediation guidance.