CWE-1267: Policy Uses Obsolete Encoding | Glexia
CWE-1267 (Policy Uses Obsolete Encoding) weakness overview with consequences, detection methods, mitigations, related CVEs and MITRE ATT&CK context.
Glexia's Take · Automated analysis
CWE-1267: Policy Uses Obsolete Encoding
Policy Uses Obsolete Encoding represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Executive Impact
- Confidentiality,Integrity,Availability,Access Control: Modify Memory,Read Memory,Modify Files or Directories,Read Files or Directories,DoS: Resource Consumption (Other),Execute Unauthorized Code or Commands,Gain Privileges or Assume Identity,Bypass Protection Mechanism,Reduce Reliability
Developer Pattern
CWE-1267 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.
Automation confidence
high confidence from CWE-1267, 4.20.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Official CWE Definition
CWE-1267: Policy Uses Obsolete Encoding
The product uses an obsolete encoding mechanism to implement access controls.
Developer And Remediation Guidance
How teams prevent and detect this weakness
Causes
- ,
Remediation
- Architecture and Design,Implementation:
Detection
- Code review
- SAST
- DAST
- Focused regression tests
Mappings
Related CVEs, CWEs, and ATT&CK context
Related CWEs
ATT&CK Relevance
ATT&CK relevance is shown only when reviewed or responsibly inferred.