vulns.co
/
GKData.io MCP and API Buy me a coffee

HackerOne · Authorization and tenant boundaries

HackerOne exports omitted internal-attachment authorization

HackerOne report exports could include team-only attachments that the report view kept private. A user still needed the ability to export that report; this was not access to every private report. HackerOne awarded $12,500 in 2016, and the lesson remains to enforce the same visibility rules in exports and interactive views.

Read the original writeupUSD 12,500 reported award · Reviewed 2026-10-03

Root cause

Export authorization diverged from report-view visibility. A file moved into an internal comment remained exportable. The researcher compared redacted display content with archive output; the vendor confirmed this was a distinct newly introduced issue.

Demonstrated impact

A user able to export a report could obtain team-only attachments. Vendor review additionally identified potential inline-attachment exposure, but found no evidence of malicious exploitation. This does not establish access to every private report.

What to check for

  • Derive export contents from the same object-level policy used for interactive views.
  • Treat referenced attachments as independently authorized objects, including after visibility changes.

Award and evidence

USD 12,500Bug Bounty · Platform Confirmed
How the award was verified, and what the record does not establish

One report-level award includes the vendor’s expanded inline-attachment impact assessment. USD uses later platform-wide payment guidance reviewed in 2026, about ten years after the award; it does not prove individual settlement. The report explicitly distinguishes earlier report 182358.

  • No independent confirmation of cash settlement.
  • Currency uses later platform-wide guidance, not an explicit currency code in the historical award event.
  • Summary uses November 28 without timezone; the report and fix events display November 29 UTC.
  • No patch implementation is disclosed.

Timeline

Published
2016-11-30explicit · Detailed report became public at the recorded disclosure event; later 2017 retrospective is not original publication.
Public Disclosure
2016-11-30explicit
Reported
2016-11-29explicit
Awarded
2016-11-30explicit
Fixed
2016-11-29explicit · Vendor fix-release comment at 04:36 UTC; researcher confirmation at 05:02 UTC. Summary says November 28 without a timezone; UTC timeline supplies the recorded date.

Related cases

All 19 cases in Authorization and tenant boundaries

Sources

  1. Internal attachments can be exported via "Export as .zip" featureHackerOne and japz · reviewed 2026-10-03
  2. Celebrating $20M in Bounties with a Recap of Our Top 20 Up Voted Reports on Hacktivityjohnk / HackerOne · reviewed 2026-10-03
  3. Vulnerability Disclosure GuidelinesHackerOne · reviewed 2026-10-03

Record reviewed 2026-10-03. Snapshot af2809c308fc. Open the complete JSON contract.

Library synced 2026-11-18 · cases last reviewed 2026-10-05

af2809c308fc · JSON exports & schemas · CC BY 4.0 content / MIT software