Wrong CWE list in X01:2025 (copied from A06)
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 6.1k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
Problem
In X01_2025-Next_Steps.md, the X01:2025 Lack of Application Resilience
section
contains an incorrect "List of Mapped CWEs".
Evidence
-
Background section (line 12) mentions relevant CWEs as:
- CWE-400 Uncontrolled Resource Consumption
- CWE-409 Improper Handling of Highly Compressed Data (Data Amplification)
- CWE-674 Uncontrolled Recursion
- CWE-835 Loop with Unreachable Exit Condition ('Infinite Loop')
-
Score table (lines 18-59) states "CWEs Mapped: 16"
-
List of Mapped CWEs section (lines 110-149) contains 39 entries:
- None of which include CWE-400, 409, 674, or 835
- The 39 CWEs listed are identical to A06:2025 Insecure Design's CWE
list
Root Cause (suspected)
The CWE list for X01:2025 appears to have been accidentally copied from A06_2025-Insecure_Design.md during document preparation.
Expected
The X01:2025 CWE list should:
- Match the count in the score table (16)
- Include the CWEs mentioned in the Background section (400, 409, 674, 835)
- Contain resilience-related CWEs appropriate for this category
Files affected
- 2025/docs/en/X01_2025-Next_Steps.md
- Section: X01:2025 Lack of Application Resilience
- Lines: 110-149 (List of Mapped CWEs)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read 2025/docs/en/X01_2025-Next_Steps.md, especially the X01:2025 section, its background and score table, then compare the mapped-CWE list with A06_2025-Insecure_Design.md. Confirm the authoritative resilience-related entries and update the list so it contains 16 CWEs, including CWE-400, CWE-409, CWE-674, and CWE-835.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100