CWE-221: Information Loss or Omission
Official CWE-221 CWE context with Glexia analysis, remediation guidance, related CVEs, and ATT&CK context.
Glexia's Take
CWE-221: Information Loss or Omission
Information Loss or Omission represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Executive Impact
- Non-Repudiation: Hide Activities
Developer Pattern
CWE-221 is the kind of defect developers can usually prevent with explicit validation, safer framework defaults, and tests that exercise hostile input or unsafe state transitions.
Confidence
high confidence from CWE-221, 4.20.
Official CWE Definition
CWE-221: Information Loss or Omission
The product does not record, or improperly records, security-relevant information that leads to an incorrect decision or hampers later analysis.
Developer And Remediation Guidance
How teams prevent and detect this weakness
Causes
- This code logs suspicious multiple login attempts. This code only logs failed login attempts when a certain limit is reached. If an attacker knows this limit, they can stop their attack from being discovered by avoiding the limit.
Remediation
- Use safe APIs
- Centralize the control
- Add regression tests
- Review logs and telemetry for attempted abuse
Detection
- Code review
- SAST
- DAST
- Focused regression tests
Mappings
Related CVEs, CWEs, and ATT&CK context
Related CWEs
- CWE-664: Improper Control of a Resource Through its Lifetime
- CWE-222: Truncation of Security-relevant Information
- CWE-223: Omission of Security-relevant Information
- CWE-224: Obscured Security-relevant Information by Alternate Name
- CWE-356: Product UI does not Warn User of Unsafe Actions
- CWE-396: Declaration of Catch for Generic Exception
- CWE-397: Declaration of Throws for Generic Exception
- CWE-451: User Interface (UI) Misrepresentation of Critical Information
ATT&CK Relevance
ATT&CK relevance is shown only when reviewed or responsibly inferred.