Title: It started on March 17th, 2022 and was resolved on May 26th, 2023.<p>What was potentially exposed?
User account information and order details including names, physical addresses, email, phone numbers.<p>Your system76.com credentials and credit card were not compromised at any point. It was not the contents of our entire database, but a random selection of what happened to be in our web servers&#x27; memory at the time. It is not possible to determine which users had their information visible over the course of time when this leak was occurring.<p>Can any of this data still be accessible?
This data was embedded directly into the source code of our website, so it will be included in any archives that were taken during this time period. We have already been in contact with the internet archive, and they have removed their data, but there are other potential places where it could have been stored.<p>What pages on our site contained this data?
Due to the nature of the flaw, the data was being included to some extent on every page on our site.<p>Why was there a delay before resolving this and making an announcement?
We wanted to do our best to clean up any residual customer data that was easily accessible before disclosing the nature of this leak. This involved working with the internet archive to delete their copy of the data before public disclosure.<p>Is there any evidence that any of this data was misused?
To date, the only indications of misuse that we have are reports of spam emails being sent to customers.<p>Why did it take so long to discover?
There were a number of factors that play into this, but they do not change the fact that it should not have been happening for over a year.<p>You would need to look at just the right location in a very long single-line string. This is a common method for minimizing javascript and most developers are used to seeing such long lines on a website. There&#x27;s usually not much reason to look into them in more detail.
    It was not something a dev would ever see in their local environment. It was also not noticeable in our staging environment due to the difference in activity there.
    It is entirely unexpected to see sensitive data exposed in this fashion.<p>What are the technical details?
One of the technologies that we use on our website is server-side rendering with nuxt. Several years ago a caching layer was implemented so that the server-side rendering wouldn&#x27;t have to ask our backend API every time it needed the same information. It worked fine, but front-end technologies shifted and the way it was implemented became outdated.
Last year our team made an update to a seemingly unrelated piece of code, to fix a deprecation message no less. However, this exposed the initial implementation of this cache to a new style of handling state, which it had not been written for and was not prepared to handle.
So what happened is the following: state that shouldn&#x27;t have been shared was shared between sessions. This is one of the major pitfalls of using server-side rendering in a web application. Unlike an API, the code in an SSR application doesn&#x27;t always have distinct boundaries between what happens on a single client vs. what happens on the server.<p>What is being done to prevent similar leaks in the future?
For the time being we are running an automated scan to alert us if sensitive data is ever found on our website again. We are also continually performing manual inspections to make sure nothing else is in there that shouldn&#x27;t be, but we are confident that we have identified and fixed this issue.
In the long term, we are moving towards a static model (SSG instead of SSR) for our website, which will eliminate the majority of the risk of shared state.<p>This is a mistake that we will learn from and we offer our sincerest apologies for leaking information that was entrusted to us. We deeply regret the incident and remain committed to safeguarding your information and trust.
Upvote: