Skip to content
Explanation

CVD Case State Interactions with the RM and EM Process Models

The specification governs

This page explains the design of the Vultron Protocol. It is informative: the normative text is the Vultron Protocol Specification. Where this page and the specification differ, the specification governs.

The Report Management (RM) and Embargo Management (EM) models interact with the Case State (CS) model of a Coordinated Vulnerability Disclosure (CVD) case. This page reviews the constraints that arise when each CS transition event occurs. The page has one section for each CS event. Each section tells how that event interacts with the RM and EM models.

Formulas use \(q^{rm}\) for the RM state of a Participant, \(q^{em}\) for the EM state of the case, and \(q^{cs}\) for the case state. The RM process model introduces the RM state abbreviations. The EM formal model defines the EM state abbreviations.

CS States defines the case-state strings such as \(VFdpxa\). It also defines the dot (\(\cdot\)), which stands for any value of one substate, as in \(VF\cdot pxa\).

CS Transition Symbols Defined

\(\Sigma^{cs} = \{ \mathbf{V},~\mathbf{F},~\mathbf{D},~\mathbf{P},~\mathbf{X},~\mathbf{A} \}\)

The CS model transition symbols are reproduced in the inset at right. They stand for Vendor awareness (V), fix ready (F), fix deployed (D), public awareness (P), exploit public (X), and attacks observed (A).

Global vs. Participant-Specific Aspects of the CS Model

The CS model has both Participant-specific and Participant-agnostic parts. The Vendor fix path substates are specific to each Vendor Participant in a case. These substates are Vendor unaware (vfd), Vendor aware (Vfd), fix ready (VFd), and fix deployed (VFD).

The remaining substates are Participant-agnostic facts about the case: public awareness (p,P), exploit public (x,X), and attacks observed (a,A). So the V, F, and D events below happen once per Vendor, while P, X, and A happen once per case. This distinction matters in the Formal Protocol definition.

The diagram below shows the two parts of the CS model side by side.

---
title: Case State Diagram showing Participant-Agnostic and Participant-Specific Aspects
---
stateDiagram-v2
    direction LR
    CS: Case State Model
    state CS {
        ps: Participant-Specific
        state ps {
            [*] --> vfd
            vfd --> Vfd : V
            Vfd --> VFd : F
            VFd --> VFD : D
            VFD --> [*]
        }
        --
        g: Participant-Agnostic 
        state g {
            [*] --> pxa

            pxa --> Pxa : P
            pxa --> pXa : X
            pxa --> pxA : A

            pXa --> PXa : P
            pXa --> pXA : A

            pxA --> PxA : P
            pxA --> pXA : X

            Pxa --> PxA : A
            Pxa --> PXa : X

            pXA --> PXA : P
            PXa --> PXA : A
            PxA --> PXA : X
            PXA --> [*]
        }
    }
    [*] --> CS
    CS --> [*]

Vendor Notification

Vendor Notification Formalized
\[q^{rm} \in S \xrightarrow{r} R\]
\[q^{cs} \in vfd\cdot\cdot\cdot \xrightarrow{\mathbf{V}} Vfd\cdot\cdot\cdot\]

Vendor Awareness (V) occurs when a Participant in RM Accepted notifies the Vendor. This Participant is typically a Finder, a Coordinator, or another Vendor. The Vendor then starts in \(q^{rm} = Received\) and follows its validation and prioritization routines. RM Interactions Between CVD Participants describes this in more detail.

The diagram below shows how the RM state of the notifying Participant enables the RM transition of the Vendor. That RM transition implies the CS Vendor Awareness event.

---
title: Vendor Notification
---
stateDiagram-v2
    direction LR
    state AnyParticipant {
        state RM {
            A: Accepted
        }
    }
    state VendorParticipant {
        RM2: RM
        state RM2 {
            direction LR
            Start --> Received : Receive report
        }

        state CS {
            direction LR
            vfd: Vendor Unaware
            Vfd: Vendor Aware
            vfd --> Vfd : Vendor Awareness
        }
        RM2 --> CS: implies
    }
    AnyParticipant --> VendorParticipant: enables

The EM process begins when the case is created, not when a Vendor is notified (ADR-0096: A Protocol Default Embargo Replaces the Pre-Case Phase). An embargo-eligible case begins with an Active embargo at case creation. The terms come from the published default of the recipient, the proposed terms of the sender, or the protocol default (Vultron Protocol Specification §7.2 Transitions and Guards). When a Vendor gets the notification, the state of the embargo therefore depends on who created the case:

For example, a Reporter and Coordinator might have already agreed to a disclosure timeline. In a multi-party CVD case, other Vendors can already coordinate the case under an embargo. They can then find, late in the case, that they must engage a new Vendor. This second example is consistent with public narratives about the Meltdown/Spectre vulnerabilities.

An embargo can also end early, before a later Vendor gets the notification. So Exited is also possible. A case that was not embargo-eligible when it was created stays in EM None.

Any outstanding embargo revision SHOULD be decided (accept, reject) soon after a newly notified Vendor joins the case.

The diagram below shows the embargo states a Vendor can find when it becomes aware of the case.

---
title: Embargo State at Vendor Awareness
---
stateDiagram-v2
    direction LR
    state Vendor {
        state CS {
            vfd --> Vfd
        }
    }
    state EM {
        Active --> Revise : propose
        Revise --> Active : accept
        Revise --> Active : reject
        Active --> eXited : terminate
        Revise --> eXited : terminate
    }
    Vendor --> EM: finds embargo<br/>already begun
Embargo State at Vendor Awareness Formalized

For an embargo-eligible case,

\[q^{cs} \in Vfd\cdot\cdot\cdot \implies q^{em} \in \begin{cases} Active \\ Revise \begin{cases} \xrightarrow{accept} Active \\ \xrightarrow{reject} Active \\ \end{cases} \\ eXited \\ \end{cases}\]

Fix Ready

Fix Readiness (F) can occur only when a Vendor is in the RM Accepted state. In multi-party cases, each affected Vendor has its own RM state. Thus, this constraint applies to each Vendor individually.


With respect to EM, when the case state is \(q^{cs} \in VF\cdot pxa\), it is usually too late to start a new embargo.

Once a case has reached Fix Ready (\(q^{cs} \in VF\cdot pxa\)),

  • New embargo negotiations SHOULD NOT start.
  • Proposed but not-yet-agreed-to embargoes SHOULD be rejected.
  • The one exception is a brief embargo to prepare for timely publication or deployment. While the fix is not yet deployed (\(q^{cs} \in VFdpxa\)), Participants MAY propose or accept such an embargo.
  • Existing embargoes (\(q^{em} \in \{Active,~Revise\}\)) MAY continue but SHOULD prepare to terminate soon.

The diagram below shows the EM transitions that remain available once a fix is ready.

---
title: Fix Ready
---
stateDiagram-v2
    direction LR
    state CS {
        Vfd: Vendor Aware
        VFd: Fix Ready
        Vfd --> VFd : Fix becomes ready
    }
    state EM {
        state PreEmbargo{
            P: Proposed
            N: None
            P --> N: reject
        }
        state ActiveEmbargo {
            A: Active
            R: Revise
            A --> R: propose
            R --> A: accept
        }
    }
    CS --> EM: implies
Embargo Effects of Fix Readiness Formalized
\[q^{cs} \in VF\cdot pxa \implies q^{em} \in \begin{cases} None \\ Proposed \xrightarrow{reject} None \\ Active \\ Revise \\ \end{cases}\]

In multi-party cases, where some Vendors are likely to reach \(q^{cs} \in VF\cdot\cdot\cdot\cdot\) before others,

  • Participants MAY propose an embargo extension to allow trailing Vendors to catch up before publication.
  • Participants SHOULD accept reasonable extension proposals for such purposes when possible (e.g., when other constraints could still be met by the extended deadline).

Fix Deployed

For vulnerabilities in systems where the Vendor controls deployment, the Fix Deployment (D) event can only occur if the Vendor is in \(q^{rm} = Accepted\).

The diagram below shows how the RM Accepted state of the Vendor enables deployment.

---
title: Fix Deployed RM-CS Interactions
---
stateDiagram-v2
    direction LR
    state RM {
        Accepted
    }
    state CS {
        VFd: Fix Ready
        VFD: Fix Deployed

        VFd --> VFD : Deploy
    }
    RM --> CS: enables

In some systems, the software delivery model requires Public Awareness before Deployment (\(\mathbf{P} \prec \mathbf{D}\)). For vulnerabilities in these systems, the Vendor status at the time of deployment might be irrelevant. This statement assumes that the Vendor passed through \(q^{rm} = Accepted\) at some point. Fix Ready (F) requires that state, and Fix Ready is a prerequisite for deployment (D).


As regards EM,

By the time a fix has been deployed (\(q^{cs} \in VFD\cdot\cdot\cdot\)),

  • New embargoes SHOULD NOT be sought.
  • Any existing embargo SHOULD terminate.

The diagram below shows the EM transitions implied by fix deployment.

---
title: Fix Deployed CS-EM Interactions
---
stateDiagram-v2
    direction LR
    state CS {
        VFd: Fix Ready
        VFD: Fix Deployed

        VFd --> VFD : Deploy
    }
    state EM {
        state PreEmbargo{
            Proposed --> None: reject
        }
        state ActiveEmbargo {
            Active --> eXited: terminate
            Revise --> eXited: terminate
        }
    }
    CS --> EM: implies
Embargo Effects on reaching Fix Deployment Formalized
\[q^{cs} \in {VFD} \cdot\cdot\cdot \implies q^{em} \in \begin{cases} None \\ Proposed \xrightarrow{reject} None \\ Active \xrightarrow{terminate} eXited \\ Revise \xrightarrow{terminate} eXited \\ \end{cases}\]

As with the Fix Ready scenario above, multi-party cases may have Vendors in varying states of Fix Deployment. Therefore the embargo extension caveats from that section also apply to the Fix Deployed state.

Public Awareness

In a coordinated publication process, (P) requires at least one Participant in the \(q^{rm} = Accepted\) state. The reason is that Participants are presumed to publish only on cases that they have accepted. Ideally, the Vendor is one of those Participants. But as the CERT Guide to Coordinated Vulnerability Disclosure explains, the Vendor does not have to be one of those Participants.

That said, the publishing party might be outside of any existing coordination process. For example, a report can already be in a CVD process when a party outside the CVD case makes the vulnerability public. Parallel discovery and embargo leaks are two causes of this situation.


As for EM, the purpose of an embargo is to prevent P until the case reaches other objectives, such as \(q^{cs} \in VF\cdot px \cdot\). Therefore,

Once Public Awareness has happened and the case state reaches \(q^{cs} \in \cdot\cdot\cdot P \cdot\cdot\),

  • New embargoes SHALL NOT be sought.
  • Any existing embargo SHALL terminate.

The diagram below shows the EM transitions implied by public awareness.

---
title: Public Awareness CS-EM Interactions
---
stateDiagram-v2
    direction LR
    state CS {
        p: Public Unaware (p)
        P: Public Aware (P)

        p --> P : Public Awareness
    }
    state EM {
        state PreEmbargo{
            Proposed --> None: reject
        }
        state ActiveEmbargo {
            Active --> eXited: terminate
            Revise --> eXited: terminate
        }
    }
    CS --> EM: implies
Embargo Effects on reaching Public Awareness Formalized
\[q^{cs} \in \cdot\cdot\cdot P \cdot\cdot \implies q^{em} \in \begin{cases} None \\ Proposed \xrightarrow{reject} None \\ Active \xrightarrow{terminate} eXited \\ Revise \xrightarrow{terminate} eXited \\ \end{cases}\]

Exploit Public

Exploit publishers may also be presumed to have a similar RM state model for their own work. Therefore, they can be expected to be in an RM Accepted state at the time of exploit code publication (X). However, those who publish exploit code cannot be presumed to be Participants in a pre-public CVD process. That said,

Exploit Publishers who are Participants in pre-public CVD cases (\(q^{cs} \in \cdot\cdot\cdot p \cdot\cdot\)) SHOULD comply with the protocol described here, especially when they also fulfill other roles (e.g., Reporter, Coordinator, Vendor) in the process.

For example, A State-Based Model for Multi-Party Coordinated Vulnerability Disclosure describes a preference for \(\mathbf{P} \prec \mathbf{X}\). This preference dictates that

Exploit Publishers SHOULD NOT release exploit code while an embargo is active (\(q^{em} \in \{A,R\}\)).

The diagram below shows that an Active or revising embargo rules out exploit publication.

---
title: Exploit Public EM-RM Interactions for Exploit Publishers
---
stateDiagram-v2
    direction LR
    state EM {
        state ActiveEmbargo {
            direction LR
            Active
            Revise
            Revise --> Active
            Active --> Revise
        }
    }
    nox: Do not publish exploit
    EM --> nox

The CS transitions establish that public exploit code is either preceded by Public Awareness (P) or immediately leads to it. Therefore,

Once Exploit Publication has occurred and the case state reaches \(q^{cs} \in \cdot\cdot\cdot\cdot X \cdot\),

  • New embargoes SHALL NOT be sought.
  • Any existing embargo SHALL terminate.

The diagram below shows the EM transitions implied by exploit publication.

---
title: Exploit Public CS-EM Interactions
---
stateDiagram-v2
    direction LR
    state CS {
        x: No Public Exploit (x)
        X: Exploit Public (X)

        x --> X : Exploit Publication
    }
    state EM {
        state PreEmbargo{
            Proposed --> None: reject
        }
        state ActiveEmbargo {
            Active --> eXited: terminate
            Revise --> eXited: terminate
        }
    }
    CS --> EM: implies
Embargo Effects on reaching Exploit Public Formalized
\[q^{cs} \in \cdot\cdot\cdot\cdot X \cdot \implies q^{em} \in \begin{cases} None \\ Proposed \xrightarrow{reject} None \\ Active \xrightarrow{terminate} eXited \\ Revise \xrightarrow{terminate} eXited \\ \end{cases}\]

Attacks Observed

Nothing in this or any other CVD process model should be interpreted as constraining adversary activity.

Participants MUST treat attacks as an event that could occur at any time and adapt their process as needed in light of the available information.

As Early Termination explains, an embargo during attacks often helps adversaries more than defenders. But the CS transitions also note that narrowly scoped attacks do not always mean that many adversaries know about the vulnerability. In such scenarios, early embargo termination leads to publication, which can help other adversaries more than defenders. The protocol therefore lets Participants use their judgment, based on their situation awareness for the case. Formally,

Once Attacks have been observed and the case state reaches \(q^{cs} \in \cdot\cdot\cdot\cdot\cdot A\),

  • New embargoes SHALL NOT be sought.
  • Any existing embargo SHOULD terminate.

The diagram below shows the EM transitions implied by observed attacks.

---
title: Attacks Observed CS-EM Interactions
---
stateDiagram-v2
    direction LR
    state CS {
        a: No Attacks Observed
        A: Attacks Observed

        a --> A : Attack Observation
    }
    state EM {
        state PreEmbargo{
            Proposed --> None: reject
        }
        state ActiveEmbargo {
            Active --> eXited: terminate
            Revise --> eXited: terminate
        }
    }
    CS --> EM: implies
Embargo Effects on reaching Attacks Observed Formalized
\[q^{cs} \in \cdot\cdot\cdot\cdot\cdot A \implies q^{em} \in \begin{cases} None \\ Proposed \xrightarrow{reject} None \\ Active \xrightarrow{terminate} eXited \\ Revise \xrightarrow{terminate} eXited \\ \end{cases}\]