feat(mapping): auto-link attacks to CREs via CWE references (Phase 2) #719
+276
−4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This PR implements Phase 2 of the OWASP Attacks integration plan (Issue 471).
It introduces automated linking logic that parses CWE references from Attack descriptions and creates Related links to the corresponding CREs.
This allows OpenCRE to leverage existing CWE mappings to automatically organize OWASP Attack content without manual curation.
Files Changed
Changes
1. Automated Linking Utility (application/utils/attack_mapper.py)
CWE-89) from Attack descriptions2. Database Safety (application/database/db.py)
sectionattribute (e.g. Attack nodes).AttributeErrorduring ingestion and improves robustness for non-standard node types.3. Verification Script (application/manual_seed_attacks.py)
CWE -> CRErelationship (CWE-22 -> Input Validation)Verification
Executed locally:
Path Traversal -> Input Validation (via CWE-22)
Path Traversalnode created.CWE-22reference.Graceful handling of missing CWEs (e.g. CWE-89)
SQL InjectionwithCWE-89.CWE-89is missing.No runtime errors when processing Attack nodes
db.pylogging fix prevented crashes.Partially fixes #471