2023 · United States · H - Transport and storage · Nation-state APT intrusion via exploited internet-facing application and firewall
Analysed 2026-11-06 by Hermes
Open this case in the tool →Nation-state APT intrusion via exploited internet-facing application and firewall
Expertise to Execution
Evidence coverage: 4/6 stages, weight 28/60
Decisive stage: entry (clearest evidence) · Alternative: Strategy to Execution
(1) As a US aeronautical-sector organization inside the critical-infrastructure perimeter, the standing expectation was boundary hygiene and scoping readiness: patch known exploited vulnerabilities on internet-facing systems (the CISA KEV program had set a 3 January 2023 remediation deadline for the Fortinet CVE) and know where its crown-jewel data sits so an intrusion can be scoped. (2) In practice multiple nation-state APT actors entered through an unpatched public-facing Zoho ManageEngine ServiceDesk Plus server (CVE-2022-47966, from as early as 18 January 2023) and an unpatched Fortinet FortiOS firewall (CVE-2022-42475, VPN activity 1-16 February 2023, after the KEV due date), took root, dumped credentials, moved laterally with PsExec and web shells to web and OWA servers, and CISA's own incident response team (February-April 2023, at the victim's request) could not determine whether data had been accessed, altered or exfiltrated. (3) Both exploited vulnerabilities were published, vendor-patched and KEV-listed with remediation deadlines before or at the intrusion, and the dataset records no zero-day: the remedy sat with technical specialists and was simply not realized on internet-facing assets - a gap wholly within the material column (Expertise to Execution), the classic knowing-doing failure of leaving known fixes unexecuted; the classification rests on the entry stage (primary-documented and load-bearing), with the containment gap amplifying the blast radius and the logging gap obscuring the scope. A secondary Strategy to Execution pattern sits in the egress stage: the governance artefact of a defined central data location never existed, which is why impact could not be scoped; it is contributing only, so it does not reach the tie-break. The entry vector here is not unknown - it is documented - but the DV follows from the unexecuted remedy, not from the attackers' technique. RM18 (Expertise to Execution lens): the two exploited vulnerabilities were known and remediable - vendor patches plus KEV listing with deadlines - yet the internet-facing ManageEngine server and Fortinet firewall stayed exploitable for weeks to months, so the known fix was never executed (causal role: Enabling). RM30 (Expertise to Execution lens): containment capability was materially insufficient - CyberScoop, quoting the advisory, reports the organization lacked proper network segmentation, and the advisory documents movement from the compromised edge hosts to internal web servers and the OWA server, giving multiple APT groups a disproportionate blast radius (causal role: Amplifying). RM33 (Expertise to Execution lens): NAT IP logging was not enabled, sensor coverage was limited and actors deleted logs from several critical servers, so neither the victim nor CISA could reconstruct follow-on exploitation or determine exfiltration (causal role: Obscuring). RM16 (Expertise to Execution lens): because the organization had not defined where its data was centrally located, responders could not identify which data the actors could reach and the exfiltration question was left permanently open (causal role: Amplifying).
RM18 — Vulnerability / patch latencyRM30 — Segmentation / containment weaknessRM33 — Logging / forensic-readiness gapRM16 — Data governance / minimisation gapVictim is unnamed: the CISA/FBI/CNMF advisory (AA23-250A, 7 Sep 2023) calls it an Aeronautical Sector organization; a CISA official told CyberScoop it is involved in the broader aviation sector. Attribution: the joint advisory names no state; the Iranian context comes from US Cyber Command's release as reported by BleepingComputer (the release page as opened today carries the advisory text without the Iranian wording), so Iran is a reported framing, not incident-level attribution; the dataset lists initiator_name Unknown, initiator_country Iran. The Cybercom release states the CSA was released 30 Aug and publicized 7 Sep 2023. The Fortinet foothold used disabled but legitimate administrative credentials of a former contractor; the account had been disabled before the activity, so no account-lifecycle marker is coded (the advisory's own mitigation asks to remove disabled accounts entirely). Exfiltration was never confirmed: TLS sessions on TCP 10443 indicated data transfer from the firewall, but no source states data was taken; the egress gap coded here is the inability to scope, not proven theft. The case file's remaining source_url entries (securityaffairs, thehackernews, darkreading, govinfosecurity) cover the same advisory or related campaigns and were not needed. No related_rows in the case file. Link check: cybercom.mil blocks automated access (HTTP 403); the page was opened and read during research.