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

Meta · Information exposure and response privacy

Instagram client configuration exposed an application credential

Instagram included an application credential in interface configuration sent to the client. The researcher reports access to application-role metadata; Meta confirms the exposure but says independent protections limited further impact and it found no abuse. Meta confirmed a $30,000 base award, with the researcher's separately listed bonuses excluded from this record.

Read the original writeupUSD 30,000 reported award · Reviewed 2026-10-02

Root cause

Server-delivered interface configuration exposed an application credential to a client. The researcher distinguished application-level authority from ordinary client-token authority, identifying a mismatch between the data needed for rendering and the privilege carried by an embedded credential.

Demonstrated impact

The researcher reports retrieving application-role metadata. Meta confirms credential exposure but says independent protections limited further impact and it found no evidence of abuse. Unrestricted administration, account takeover and actual customer compromise were not established.

What to check for

  • Classify every credential by its authority and intended holder before deciding whether it belongs in client-visible data.
  • Keep privileged application credentials inside controlled server contexts; minimize the capabilities available to client integrations.
  • Preserve independent authorization checks after credential validation, and distinguish the demonstrated exposure from hypothetical downstream consequences.
  • Treat containment and least-privilege recommendations as design guidance; the sources do not document the complete vendor patch.

Award and evidence

USD 30,000Bug Bounty · Vendor Confirmed
How the award was verified, and what the record does not establish

Records the vendor-confirmed base once. The researcher separately lists $6,000 league, $2,250 delay and $50 event bonuses; these are not added to this amount or counted as separate findings. USD uses earlier official program denomination context; settlement is unknown.

  • The vendor confirms the base; bonus breakdown and report/award timeline are researcher-reported.
  • Original researcher publication and exact fix deployment are uncertain; the vendor bulletin supplies the publication date used here.
  • The currency reference is older program context, not a report-specific settlement record.
  • No full patch implementation or unrestricted downstream compromise is established.

Timeline

Published
2022-07-20explicit · Dated vendor publication is used. The researcher page presents February 24, 2022 and August 27, 2024 without a clearly extracted original-versus-update label; its original public release remains uncertain.
Public Disclosure
2022-07-20explicit · Vendor discussion and direct researcher link establish public availability by this date, not the earliest possible disclosure.
Reported
2022-02-24explicit
Awarded
2022-05-19explicit
Award Announced
2022-07-20explicit · Public vendor confirmation; an earlier researcher announcement is possible.

Related cases

All 3 cases in Information exposure and response privacy

Sources

  1. How Meta and the security industry collaborate to secure the internetMeta Engineering · reviewed 2026-10-02
  2. Instagram App Access TokenPhilippe Harewood · reviewed 2026-10-02
  3. Facebook Bug Bounty and BountyCon US-dollar reportingDan Gurfinkel / Facebook · reviewed 2026-10-02

Record reviewed 2026-10-02. 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