You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: crowdsec-docs/unversioned/tracker_api/exploitation_phases.mdx
+54-14Lines changed: 54 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ Every tracked CVE and fingerprint rule is assigned an **exploitation phase** tha
9
9
10
10
The phases are determined by analyzing exploitation telemetry from the CrowdSec Network over time — they reflect real attacker behavior, not theoretical risk.
11
11
12
-
## The Five Phases
12
+
## The Phases
13
13
14
14
### Insufficient Data
15
15
@@ -19,6 +19,22 @@ This is the starting state for newly tracked CVEs or those affecting products wi
19
19
20
20
**What to do**: Fall back to traditional risk indicators (CVSS score, public exploit availability, vendor advisory severity) until CrowdSec telemetry matures for this CVE. Check back periodically as the phase will update when sufficient data is collected.
21
21
22
+
### Early Exploitation
23
+
24
+
> *"Early exploitation attempts have been observed, but activity remains limited and not yet widespread."*
25
+
26
+
CrowdSec is picking up the first real signals — scan traffic or small-scale exploit attempts. It's not yet a campaign. This phase often appears in the days after a public PoC drops for a CVE that hasn't been widely weaponized yet.
27
+
28
+
**What to do**: Begin prioritizing this CVE for patching. The window between Early Exploitation and a broader campaign can be short — track momentum closely and reassess frequently.
29
+
30
+
### Fresh and Popular
31
+
32
+
> *"The vulnerability is recent and currently shows strong attacker interest with rapidly increasing exploitation activity."*
33
+
34
+
This CVE is gaining rapid traction in the attacker community. Volume is growing fast and multiple actors are experimenting with it. It may be on the verge of tipping into Mass Exploitation.
35
+
36
+
**What to do**: Treat this as high urgency. Patch immediately if possible. Deploy blocklists proactively — don't wait for confirmed hits on your infrastructure.
37
+
22
38
### Unpopular
23
39
24
40
> *"The vulnerability is known but shows very limited attacker interest or exploitation activity."*
@@ -53,39 +69,60 @@ The vulnerability has been weaponized at scale. Multiple threat actor groups are
53
69
54
70
**What to do**: Treat this as an emergency if you haven't patched yet. Verify patch status across your entire estate. Deploy blocklists immediately. Monitor for signs of compromise, as exploitation may have occurred before you acted.
55
71
72
+
### Wearing Out
73
+
74
+
> *"Exploitation activity is decreasing over time, likely due to patch adoption or reduced attacker interest."*
75
+
76
+
The peak campaign has passed. Patch adoption is reducing the attack surface and/or attackers have moved on. Activity is still present but on a clear downward trend.
77
+
78
+
**What to do**: If you haven't patched yet, do it now while the pressure is lower. This phase is a second chance — exploitation is easier to attribute and less noisy than at peak.
79
+
56
80
## Phase Transitions
57
81
58
82
CVEs don't always move linearly through these phases. Common patterns include:
59
83
60
-
-**Newly published CVE with public exploit**: May jump directly from *Insufficient Data* to *Targeted Exploitation* or *Mass Exploitation* if attackers weaponize it quickly.
61
-
-**Old CVE with new exploit toolkit**: A CVE that was *Background Noise* for years can escalate to *Mass Exploitation* when it gets added to a popular exploit framework.
62
-
-**Campaign ends**: A CVE in *Mass Exploitation* can settle back to *Background Noise* once the initial campaign runs its course and most targets are patched.
63
-
-**Steady state**: Many CVEs stabilize in *Background Noise* indefinitely — they remain part of automated scanning toolkits long after the initial threat subsides.
84
+
-**New PoC drops**: A CVE moves from *Insufficient Data* to *Early Exploitation* within days of a public proof-of-concept being published.
85
+
-**Rapid weaponization**: *Early Exploitation* escalates to *Fresh and Popular* when multiple threat actors adopt the CVE simultaneously.
86
+
-**Fresh and Popular → Mass Exploitation**: The most common escalation path for high-impact CVEs in widely deployed software when no effective mitigation is available.
87
+
-**Fresh and Popular → Wearing Out**: Some CVEs peak quickly and decline before ever reaching mass scale — the community patches fast or the target surface is limited.
88
+
-**Old CVE with new exploit toolkit**: A CVE in *Background Noise* for years can escalate to *Targeted Exploitation* or *Mass Exploitation* when added to a popular exploit framework.
89
+
-**Campaign ends → Wearing Out**: After a *Mass Exploitation* or *Targeted Exploitation* campaign concludes, activity enters a decline.
90
+
-**Wearing Out → Background Noise**: Residual automated scanning typically continues long-term, settling into steady-state low-level activity.
Targeted Exploitation is the most predictable: it consistently shows high Opportunity scores (4–5) and elevated CrowdSec Scores. Other phases are more loosely correlated — Background Noise and Unpopular overlap significantly in score ranges, and Mass Exploitation spans a wide range depending on whether the campaign is ramping up or fading.
149
+
Targeted Exploitation is the most predictable: it consistently shows high Opportunity scores (4–5) and elevated CrowdSec Scores. Fresh and Popular stands out for its high Momentum (4–5), reflecting the rapid growth in activity. Wearing Out is characterized by low and falling Momentum. Other phases are more loosely correlated — Background Noise and Unpopular overlap significantly in score ranges.
0 commit comments