2017 · United States · O - Public administration and defence · Website defacement across the state government web estate
Analysed 2026-11-06 by Hermes
Open this case in the tool →Website defacement across the state government web estate
Expertise to Execution
Evidence coverage: 2/6 stages, weight 12/60
Decisive stage: entry (clearest evidence) · Alternative: Strategy to Execution
(1) The expectation at the victim sat at the technical level: Ohio ran its public web estate, including the governor's site, on DNN Platform, a CMS popular with state and local government, and DNN had published a critical security update in May 2016 warning that attackers could create new SuperUser accounts on the outdated version and urging customers to upgrade. (2) In practice the estate was still on DNN 7.0 (2015) thirteen months after that update; on 25 June 2017 Team System DZ used the patched flaw to deface governor.ohio.gov and the sites of ten other agencies - 10 sites on two state servers - and the state's own count plus Ars Technica's HTML-source review show every attacked site ran the same outdated platform. (3) The remedy was known, published and executable by the specialists running the CMS; the chain broke where the known upgrade was never realised in operations and architecture, not in a leadership decision - no source shows patching deferred, underfunded or accepted as a risk by leadership, and no Ohio policy artefact is documented that would make this a strategy-to-execution case - so the decisive gap (entry) is material origin with an execution break. The entry vector is not merely pattern here: it was verified per site in press source analysis, and Ohio's own statements confirm the blast radius. Detection, egress, recovery and response show no victim-side gap: the visible defacement was acted on within hours, no data was accessed, all sites were back by the next morning and the public account matched the facts. RM18 (Expertise to Execution lens): the vulnerability was known and remediable - DNN's May 2016 critical update warned of exactly the SuperUser-account takeover used - yet the state's CMS instances stayed on version 7.0 for about thirteen months, so remediation execution never caught up with the published fix (causal role: Enabling). RM04 (Expertise to Execution lens): the state's web presence concentrated ten agencies' public sites on two state servers sharing one outdated CMS platform, and the dependency was never reduced through the intervening updates, so one platform-level compromise defaced the whole estate at once and forced all affected servers offline as a precaution (causal role: Amplifying).
RM18 — Vulnerability / patch latencyRM04 — Control dependency concentrationEuRepoC row; victim named from the row's name/description (governor's office of Ohio) - the incident actually hit a 10-11-site Ohio web estate (governor, first lady, lieutenant governor, inspector general, Medicaid, corrections, casino control, LeanOhio, workforce/health transformation, facilities). The DNN entry mechanism was established by Ars Technica's review of the HTML source of each attacked site and corroborated by SecurityWeek and Bitdefender's blog, but Ohio never officially confirmed the vector and did not respond to Ars for comment; SecurityWeek noted uncertainty about sites beyond those Ars analysed. The group's ISIS affiliation is unverified - press and researchers describe Team System DZ as a self-styled pro-ISIS crew (self-attribution via defacement statements; EuRepoC attribution basis: attacker confirms). Per EuRepoC the incident was disclosed by the attacker; the state's own statements followed the same day and are not counted as a disclosure gap because a public defacement discloses itself. cleveland.com reported the same restoration/no-data facts but returned HTTP 403 to automated fetching and is not cited; cnn.com failed to fetch and is not cited. Link check: thehill.com blocks automated access (HTTP 403); the page was opened and read during research. Unattended run: nothing in this case required an action with consent.