← Breach analysis by the Dual Vulnerabilities framework

WSDOT Online Services Disruption (Unattributed, 2023)

2023 · United States · O - Public administration and defence · Cyberattack causing multi-day disruption of public web services

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Cyberattack causing multi-day disruption of public web services

Dual vulnerability type

No DV evidenced

Alternative: none defensible

Why this classification

(1) WSDOT, a state transport agency, is expected to keep its public travel-information platform (website, app, traffic cameras, ferry vessel watch, freight permits) available and to investigate and disclose incidents affecting it. (2) On 7 November 2023 a cyberattack aimed at interrupting the flow of travel-related information took most public-facing services down for about four days, with staged restoration completed by 11 November; WaTech said there was no indication of a data breach, and WSDOT said there was no indication the attack spread beyond the outward-facing website. (3) Despite the search, no lifecycle stage yields a defensible victim-side mechanism: the cause was never publicly identified (every report repeats that the cause remained under investigation), the investigation was run only by WSDOT's own IT team and the incident was not turned over to law enforcement (while WSDOT also said it worked in close coordination with federal partners), no group claimed the attack and WSDOT offered no attribution, detection timing was not disclosed, containment was stated to have held, egress was not in play (no data breach), recovery completed within days using manual fallbacks (handwritten freight permits at 13 locations, social-media travel updates) with no missing arrangement identified, and disclosure was self-initiated via the department's own channels. Under the decision rule, this is the reporting-confirms-impact-only / cause-stated-undetermined case: the DV-Type is Unknown, not a claim that no vulnerability existed. The entry vector is unknown and not load-bearing; no later stage documents a knowing-doing or doctrinal-material gap either.

Sources

Notes

EuRepoC row; victim named from the incident name and reporting (receiver_name absent). Actor genuinely unattributed: no claim of responsibility and no attribution by WSDOT or WaTech in any opened source. The cause of the 7 November 2023 incident was never publicly identified in the reporting opened (Nov 2023 coverage and vendor retrospectives still describe it as under investigation), and the investigation stayed internal (Seattle Times: not turned over to law enforcement; WSDOT also said it was working in close coordination with federal partners - the two statements both appear in the same reporting). Reporting opened for follow-up found no forensic findings, regulator review or legislative scrutiny of this incident. The December 2021 WSDOT data breach is mentioned as background in the Washington State Standard article; it is a separate, distinct incident (older system, contractor-employee personal data) and the department said at the time it had addressed the flaws from it; no comparable recurring weakness is documented for the 2023 incident, so no recurring-weakness marker is coded. No related_rows in the case file; no other case file or existing result in this run covers WSDOT. Case-file fields confirm disruption longer than 24 hours, functional impact under 7 days and no data breach/exfiltration, matching the reporting. Link check: washingtonstatestandard.com blocks automated access (HTTP 403); the page was opened and read during research.