rewindex

ChangesAkamaiCustomer Security Advisory: Node.js Brotli Remote Code Execution Vulnerabilities

Akamai: Incident updated: Customer Security Advisory: Node.js Brotli Remote Code Execution Vulnerabilities

Incident updateNormal progress (rule, 100%)Changed www.akamaistatus.com (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Akamai removed; blue is what they added. Muted text is unchanged context.

ChangedStatus#1
Before: investigating
After: identified
AddedUpdateidentified#2
Before: not present
After: We will continue to investigate and evaluate any possible impact to customers and our platform over the weekend. So far the investigation has not shown evidence of customer impact caused by this vulnerability. The appropriate subject matter experts are engaged. We will continue to provide updates until we have a clearer picture about the evaluation and the mitigation plan. Subsequent updates around mitigation status will be posted as progress is made.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Rewindex captured a newer version after the last checkpoint; the next run () commits it.

History of this incident

TodaySaturday, October 24Sat, Oct 24

1 incident change

YesterdayFriday, October 23Fri, Oct 23

2 incident changes

All Akamai changesAkamai profileMarkdownJSON