ZeroHour

Search: “Amazon Now”

3 stories in the last 24h

AWS Says Some Cloud Data Cannot Be Recovered After Data Centers Suffer War Damage

AWS confirmed some customer data in war-damaged Middle East data centers is permanently unrecoverable after Iranian drone strikes hit Bahrain and UAE facilities.

Amazon Web Services said in a September 15 Health Dashboard update that it is unable to restore data hosted exclusively in its Bahrain me-south-1 region and the UAE mec1-az2 availability zone after Iranian missile and drone strikes that began in March. Damage in Bahrain spanned multiple availability zones, exceeding what AWS regional and multi-AZ services are designed to withstand. Customers without backups outside the affected footprint lost data permanently; AWS has suspended regional billing, notified authorities in both countries, and expects further UAE updates in coming months and Bahrain updates in early 2027.

Cyber Security News · 2h agoIndustry

The skb that wasn't freed - the Fragnesia primitive via Open vSwitch

Doyensec details CVE-2026-90049 in Open vSwitch, enabling deterministic Linux kernel local privilege escalation on default major distribution installs.

Doyensec reports that the Open vSwitch datapath strips the SKBFL_SHARED_FRAG flag from packets it is still forwarding, allowing an in-place decrypt to write attacker-chosen bytes into root-owned page cache — a Dirty COW-class primitive that re-opens the Fragnesia bug family. The issues are tracked as CVE-2026-90049, CVE-2026-89487, and CVE-2026-80977, and were reported to the kernel security team with fixes coordinated alongside OVS maintainers. A deterministic local privilege escalation works on default installs of Arch, Fedora, Debian, Amazon Linux, and RHEL where unprivileged user namespaces and openvswitch auto-loading are enabled; the fix landed in mainline and shipped in stable on 09/04/2026. The write technique builds on the earlier Fragnesia and Dirty Frag bugs, including CVE-2026-43284 and CVE-2026-43500.

CISA and NIST Issue Guidance to Protect Cloud Identity Tokens

CISA and NIST published Interagency Report 8587 with voluntary guidance to harden cloud identity tokens against theft, forgery, and lateral movement.

CISA and NIST released NIST Interagency Report 8587 on September 15 with final voluntary guidance for federal agencies, cloud providers, and their customers on protecting SSO, federation, and API tokens. Requirements include one-hour maximum token lifetimes, 90-day signing key rotation for high-impact systems, hardware-backed key storage, explicit audience fields, and keeping tokens out of logs. The guidance was motivated by the 2020 ADFS compromise where forged SAML assertions bypassed MFA, and an incident where a leaked consumer signing key enabled token forgery and theft of 60,000+ emails from one agency. Nearly 250 public comments shaped the text, with input from Google, Microsoft, Okta, AWS, Oracle, IBM, HashiCorp, Wiz, and the OpenID Foundation via the Joint Cyber Defense Collaborative.

Infosecurity Magazine · 23h agoAdvisory