---
title: "Bug Bounties and Black Swans: How Heroku Expects the Unexpectable"
description: "Heroku frames security as an engineering discipline that must challenge happy-path assumptions, test continuously, and prepare for low-predictability, high-consequence “black swan” events. Its threat-modeling guidance focuses on challenging defaults, recognizing that attackers have resources and organizational support, and planning for unexpected failures such as a zero-day exploit. A control-plane instrument for Heroku Postgres detected privilege escalation to a superuser role, and the Data team isolated the instance within 17 minutes while investigating the activity. The event was traced to researcher Andrew Krasichkov (“buglloc”), whose testing exposed a vulnerability in the dblink and postgres_fdw extensions. Through the Bugcrowd bug bounty program, Heroku worked with him to understand the issue, reward the finding, and defend against the previously unknown flaw before a patch was available."
---

# Bug Bounties and Black Swans: How Heroku Expects the Unexpectable

[Heroku](https://yomu.fyi/company/heroku) · Wade · Mar 26, 2019

**Type:** Explainer

## Summary

Heroku frames security as an engineering discipline that must challenge happy-path assumptions, test continuously, and prepare for low-predictability, high-consequence “black swan” events. Its threat-modeling guidance focuses on challenging defaults, recognizing that attackers have resources and organizational support, and planning for unexpected failures such as a zero-day exploit. A control-plane instrument for Heroku Postgres detected privilege escalation to a superuser role, and the Data team isolated the instance within 17 minutes while investigating the activity. The event was traced to researcher Andrew Krasichkov (“buglloc”), whose testing exposed a vulnerability in the dblink and postgres\_fdw extensions. Through the Bugcrowd bug bounty program, Heroku worked with him to understand the issue, reward the finding, and defend against the previously unknown flaw before a patch was available.

## Context

Software security can rely on unsafe assumptions about isolation, role segregation, authentication, encryption, and other controls. The brief argues that mature security programs must account for low-predictability, high-consequence events, including vulnerabilities known first to an attacker or researcher.

## Approach / What changed

Heroku combines threat modeling, automated misconfiguration testing, external security testing, control-plane instrumentation, rapid incident response, and collaboration with bug bounty researchers. In the described case, the Data team detected privilege escalation, isolated the instance within 17 minutes, and worked with Andrew Krasichkov through Bugcrowd before a patch was available.

## Takeaways

- Heroku Postgres instrumentation detected privilege escalation to a superuser role, enabling the Data team to isolate the instance within 17 minutes.
- Andrew Krasichkov’s research identified a Postgres vulnerability in the dblink and postgres\_fdw extensions.
- The Bugcrowd relationship let Heroku understand and mitigate the previously unknown flaw before a patch was released.

**Tags:** [Bug Bounty](https://yomu.fyi/topic/bug-bounty), [Incident Response](https://yomu.fyi/topic/incident-response), [Postgres](https://yomu.fyi/topic/postgres), [Threat Intelligence](https://yomu.fyi/topic/threat-intelligence)

- Source: [Heroku](https://www.heroku.com/blog/bug-bounties-black-swans)
- Source URL: https://www.heroku.com/blog/bug-bounties-black-swans
- Ingested by Yomu: 2026-09-09T14:27:16.606Z

[Read original post](https://www.heroku.com/blog/bug-bounties-black-swans)
