frameworks/docs/data/security-map/nodes/ens.json at develop · security-alliance/frameworks · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
{
  "nodes": [
    {
      "id": "surface-ens-resolution",
      "type": "attack-surface",
      "title": "ENS name resolution",
      "summary": "Turning a human-readable name into an address before a send. Stale indexers, skipped reverse checks, and confusable scripts all produce a valid-looking wrong destination.",
      "domains": ["onchain-systems"],
      "status": "proposed",
      "tags": ["ens", "resolution"],
      "roles": ["engineer-developer"],
      "lifecycle": ["normal-operations"],
      "framework": "ens"
    },
    {
      "id": "threat-spoofed-ens-resolution",
      "type": "threat",
      "title": "Spoofed ENS resolution",
      "summary": "The UI shows a trusted name while the resolved address is attacker-controlled, from a stale indexer, a reverse record that does not loop, or a homograph.",
      "domains": ["onchain-systems"],
      "status": "proposed",
      "tags": ["ens", "homograph", "spoofing"],
      "severity": "high",
      "severityBasis": "Default triage is high because the send is valid and irreversible. The bug is in resolution, not in the signature.",
      "framework": "ens"
    },
    {
      "id": "control-l1-ens-resolution",
      "type": "control",
      "title": "L1-backed ENS resolution",
      "summary": "For fund movement, resolve from Ethereum L1, not a stale indexer. Verify reverse records with a matching forward lookup before the send.",
      "domains": ["onchain-systems"],
      "status": "proposed",
      "tags": ["ens", "l1", "reverse-record"],
      "controlClass": "preventive",
      "assessmentEligible": true,
      "roles": ["engineer-developer"],
      "lifecycle": ["design", "normal-operations"],
      "framework": "ens"
    },
    {
      "id": "control-ensip15-normalization",
      "type": "control",
      "title": "ENSIP-15 name normalization",
      "summary": "Normalize names with ENSIP-15 before any namehash, and warn on confusable scripts. Homographs survive if the UI skips this.",
      "domains": ["onchain-systems"],
      "status": "proposed",
      "tags": ["ens", "normalization", "homograph"],
      "controlClass": "preventive",
      "assessmentEligible": true,
      "roles": ["engineer-developer"],
      "lifecycle": ["design", "development"],
      "framework": "ens"
    },
    {
      "id": "guidance-ens",
      "type": "guidance",
      "title": "ENS best practices",
      "summary": "Secure ENS use means fresh L1-backed resolution for funds moves, correct name normalization, and verified bidirectional records.",
      "domains": ["onchain-systems"],
      "status": "proposed",
      "tags": ["ens"],
      "href": "/ens/overview",
      "framework": "ens"
    },
    {
      "id": "guidance-ens-integrity",
      "type": "guidance",
      "title": "ENS data integrity",
      "summary": "For fund movement, resolve from Ethereum L1 and always verify reverse records with a matching forward lookup.",
      "domains": ["onchain-systems"],
      "status": "proposed",
      "tags": ["ens", "integrity"],
      "href": "/ens/data-integrity-verification",
      "framework": "ens"
    },
    {
      "id": "guidance-ens-normalization",
      "type": "guidance",
      "title": "ENS name handling",
      "summary": "Normalize with ENSIP-15 before any namehash, and warn on confusable scripts that enable homograph phishing.",
      "domains": ["onchain-systems"],
      "status": "proposed",
      "tags": ["ens", "normalization"],
      "href": "/ens/name-handling-normalization",
      "framework": "ens"
    }
  ]
}