Skip to the content
AI and Cybersecurity Learning and Practice Center Test automation Open the Learning Center

IncidentData exposure

Meta Muse: more than 6,800 shared pages were findable through passive DNS, conversation titles included

HighMetaClaroc

Claroc reported on October 18 that Muse, the Meta assistant launched on September 8, published shared content as a page on a hostname under cf.metaaiusercontent.com built from the conversation's title plus a random ID. The title was readable in the address, and the ID was logged in passive DNS when anyone opened the page, so one query to a commercial passive DNS service returned more than 6,800 share hostnames; Claroc says it guessed and brute-forced nothing and opened only a few hundred pages, in a logged-out browser. A public URL scanning service held more than 75 saved scans of Muse share pages as well. The pages Claroc describes included a candidate's preparation for an executive search call with a frontier AI lab, a marketing company's internal revenue review marked for its CEO, a small business loan application, a to-do list with a bank fraud alert and a partial account number, a real estate investor's report with two property addresses, and a workplace vacation calendar covering dozens of employees. Claroc reported it to Meta's bug bounty program on October 8 and says it had no response before publishing; after Ars Technica reported the findings on October 20, Meta paused sharing while it reviewed the report, and 40 shares Claroc rechecked that day no longer opened, though their hostnames remain in passive DNS history. On October 22 Meta's David Singleton wrote that the underlying issue was fixed and sharing was back on; artifacts shared before the fix have new addresses, and old links show a note asking for the new one. Singleton said the flaw affected shared Muse artifacts, not chat sharing, and that the Muse bug bounty pays up to 300,000 dollars for valid findings.

Replay the attack step by step in the Learning Center

How it happened

  1. Share pages lived on per-conversation hostnames, so resolvers recorded every one that was ever opened.
  2. The hostname carried the conversation title, which told anyone reading the DNS history what was worth opening.
  3. The pages needed no login, so a leaked address was the whole secret.

Impact

More than 6,800 share pages discoverable without the link, among them loan, revenue, fraud and personnel details; Claroc reports no evidence of misuse.

The fix

Meta replaced the share addresses and turned sharing back on October 22. If you shared a Muse artifact before then, the old link no longer works and anyone who needs it needs a new one from you; assume the title and the page were readable to anyone looking.

Lessons

  • Anything encoded in a hostname is public: resolvers, passive DNS feeds and scanners all keep it.
  • A link that works for anyone who has it is only private while nobody else can list the links.

Sources