Title: Under certain error conditions, a bug in our API code briefly published 84
users&#x27; usernames, email addresses, password hashes, and 100 most recent votes.
This information appeared at https:&#x2F;&#x2F;hacker-news.firebaseio.com&#x2F;v0&#x2F;updates. We
notified affected users on Monday, November 10th via email and (for users
without email addresses in their profile) on Tuesday the 11th via a message in
the site header.<p>Affected profiles were leaked on one of 10&#x2F;12, 10&#x2F;20, or 11&#x2F;02. In every case,
the leaked data was overwritten 30 seconds later by the subsequent update
batch. The leaked password hashes were salted bcrypt (FreeBSD&#x27;s default
libcrypt implementation). Though we think the risk is low we encouraged
affected users to change their password on HN as well as on any other sites
where they used the same password.<p>Many thanks to Ovidiu Toader for alerting us to the bug and for sending us
examples that assisted us in tracking it down. While the bug was fixed on
Sunday, November 9th within minutes of our becoming aware of it, Ovidiu
originally reported the issue one week prior - we just didn&#x27;t see it in a
timely manner.<p>To help improve our future response times, we&#x27;ve created a dedicated reporting
address, security@ycombinator.com that we&#x27;ll publish on our contact form.
We&#x27;re also creating a &quot;Wall of Fame&quot; to properly thank and credit past and
future vulnerability reporters. More details will follow.<p>Super sorry about this,<p>The Hacker News Team<p>(Edit)<p>A clarification, since some people seem to be misunderstanding: Only publicly available data is intentionally pushed to Firebase. That any part of a user&#x27;s profile other than their username, account age, about text, and list of submitted items was published <i>IS THE BUG</i>, and is now fixed.
Upvote: