Home / Companies / Semaphore / Blog / Post Details
Content Deep Dive

Heartbleed

Blog post from Semaphore

Post Details
Company
Date Published
Author
Marko Anastasov
Word Count
345
Company Posts That Month
4
Language
English
Hacker News Points
-
Post removed?
No
Summary

A critical security vulnerability known as Heartbleed was discovered in OpenSSL on April 7th, allowing unauthorized access to 64k chunks of memory without leaving traces in server logs. This prompted Semaphore to upgrade OpenSSL to a secure version and replace SSL certificates across their infrastructure to prevent future attacks. Although no harm was detected, Semaphore advised users to change their passwords and reset API tokens, providing a straightforward method to do so in their project settings. Additionally, they recommended enabling GitHub's two-factor authentication and resetting OAuth tokens, which was applied to all users. For those deploying to Heroku, users were informed that after changing their Heroku password, a new API token needs to be set in the server settings. Semaphore offered support through their app and email for any further concerns and invited users to discuss the issue on Discord.

Trends Found in this Post

No tracked trend matches for this post yet.

Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.