FMP-SOURCE-001 · Application reliability · Repaired

When an inherited source name cleared visible results

An unsupported source label matched an inherited object property. A supported-key check now keeps that metadata from interrupting result rendering.

Owned local code, fictional data and fresh profiles. This finding does not establish a browser-engine flaw, attacker access, customer losses or incident frequency.

What failed, and what had to be true

My People showed one fictional result and saved it. A replacement home-health record used an inherited object-property name as its location source, with the listing state and the location-evidence method and URL absent. The plain object lookup returned an inherited value, and rendering later tried to use a missing validation rule. The replacement left zero visible cards. The saved shortlist remained intact. [1]

A controlled replacement response contains a home-health listing ID and category, a locationEvidence object whose sourceId is an inherited object-property name, no listing state, and no location-evidence method or URL. The comparison uses an ordinary unknown source name with the same absent fields. No production injection, attacker access or real customer incident was established.

Transition traced: Receive → basic listing validation → commit replacement → lookup source name on a plain object → render against an inherited value → exception. This was a lookup error, not demonstrated prototype pollution or an engine isolation failure.

Accept only supported source metadata

Require the source label to be an own property of the application’s fixed source registry before consulting its validation rules. Unsupported metadata is ignored. The listing can still render, and supported source attribution is preserved.

Three inherited names and one ordinary unknown-source control were checked in each engine on exact baseline source. The six inherited-name cases changed one visible result to zero; both unknown-source controls retained one. Repaired checks require one visible result and preserved saved state for every case. [1]

The browser repair ships in My People Release 6.

Use controls, not a dramatic payload

  1. Load and save one fictional listing in an owned local copy.
  2. Return a fictional home-health replacement with its listing state absent and location evidence containing only the unsupported source label, without a method or URL.
  3. Compare an inherited property name with an ordinary unknown name, recording visible results and saved state.
  4. Repeat on repaired code and confirm supported source provenance still passes its existing tests.

Use synthetic records and an authorized local copy. Keep original failed receipts and distinguish a test-harness mistake from a product defect.

Evidence and limits

Reproduction and repair checks used Microsoft Edge 157.0.4341.46 and Playwright WebKit 26.5 on Windows. Physical Safari, iPhone, Android, native mobile keyboards and Firefox were not tested. Viewport checks do not establish physical-device behavior.

No malformed request was sent to production. The evidence shows the tested inputs and transitions; passing controls do not establish universal safety or account isolation.

[1] Original application evidence. See Browser Busters evidence, finding FMP-SOURCE-001. Exact baseline and repaired hashes, bounded private reproducers, browser receipts and failures remain in the project’s operational records. The public evidence contains no customer records or working attack code.