Research collected from outside sources and what this site derives from them; every fact links to a saved copy of its source Research or story?
Risks / R02 The coordinated disclosure broke before the fix was ready / R02-2
R02-2: Early mitigation advice to a few providers leaked
Because mitigation advice was given to a few critical-infrastructure providers from about 23:00 UTC on 20 October without, as far as the record shows, a sharing label that held, it may have leaked, resulting in a signal to attackers and an uneven head start among defenders.
Rating 9 medium · Likelihood 3 Possible · Impact 3 Significant · Kind Disclosure process · Acceptance not recorded
Basis. Reported by the Foundation as possible, not shown.
The path
Who carries it
One risk, assigned to every stakeholder that carries part of it, with the part each plays.
| Stakeholder | Part | Why | Its register |
|---|---|---|---|
| Critical infrastructure providers | source | Received the advice. | 2 risks |
| The PHP security team | owner | Chose who to tell and on what terms. | 7 risks |
| Organisations running PHP | bearer | Most received nothing early. | 26 risks |
What it arises from
- One embargo shared by many parties. Four independent finders, a coalition, early advice to critical infrastructure and image builders: every party is a place the secret can leave by.
The evidence
| Claim | Status | Fact-check | Sources |
|---|---|---|---|
| Mitigation advice given to a few critical-infrastructure providers from about 23:00 UTC on 20 October may have leaked | reported | A2 Reported●●○○○○ | PHP Foundation |
Treatments
| Treatment | Status | Where |
|---|---|---|
| Share early advice under TLP:AMBER+STRICT and record who received it | missing | How the coordinated disclosure broke |
The standards that govern it
| Framework | Control | What it asks | Family |
|---|---|---|---|
| FIRST TLP 2.0 | TLP:AMBER+STRICT | Limited disclosure: recipients share only within their organisation | Practice and technique |
| ISO/IEC 27001 | A.5.14 | Information transfer, including under agreed classification | Management-system standards |
| ISO/IEC 29147 and 30111 | 29147:coordination | Coordinating disclosure with other vendors and parties under embargo | Practice and technique |
The stories that tell it
- Where php2shell stands: many sites dark, millions of attempts, no confirmed breach (through The coordinated disclosure broke before the fix was ready)
- php2shell in perspective: an old embargo model, a Log4Shell shape, and the shrinking gap between theory and proof (through The coordinated disclosure broke before the fix was ready)
On this site: How the coordinated disclosure broke