FMP-METADATA-001 · Application reliability · Repaired

When nested source metadata interrupted a listing

An object-shaped source identifier passed the listing boundary and broke optional attribution rendering. String checks now ignore unsupported metadata while keeping the listing usable.

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

A fictional home-health replacement had the expected listing identity, state, supported source, method, URL and date. Its nested record identifier was an object instead of a string, with non-callable conversion fields. The source-identifier check tried to convert it and threw, leaving zero visible replacement cards. The prior saved shortlist stayed intact. A separately seeded saved-list test also interrupted startup while retaining the original storage bytes. [1]

The candidate requires malformed nested location evidence for a supported source, with the surrounding attribution fields matching that source. No native producer was shown to create this object shape, and no production injection or attacker access was established. The same unsupported identifier with an unknown source key was ignored in the independent control; a canonical string identifier retained legitimate attribution.

Transition traced: Receive → parse → validate ordinary listing fields → commit replacement → clear visible list → inspect optional supported-source metadata → implicit object-to-string conversion throws. On seeded startup, the same rendering step interrupts saved-list display before navigation is initialized.

Check the primitive type before source validation

Require primitive strings before validating location-evidence record IDs and dates. Apply the same check to secondary Ohio and Illinois location-source IDs and the Illinois checked date. Ignore unsupported optional metadata while retaining the underlying listing and its original saved record. Existing source, method, URL, identity and calendar checks still apply; valid source attribution remains visible.

The initial review recorded eight metadata-related observations, including four replacement/startup failures. Independent checks reproduced the supported-source failure in both engines and retained cards for valid string and unknown-source controls. All 14 repaired metadata observations passed, including twelve actual Save-and-reload journeys and adjacent malformed date or secondary-ID cases. Unit checks preserve valid Texas, Ohio and Illinois attribution while rejecting wrong types and existing mismatched evidence. [1]

The browser repair ships in My People Release 7.

Use controls, not a dramatic payload

  1. Use a fictional home-health record whose normal source identity, state, method, URL, record ID and date produce the expected attribution.
  2. Change only the nested identifier to a non-convertible JSON object. Compare the supported source with an unknown-source control.
  3. Record visible results and prior saved bytes; test preexisting saved metadata separately from a normal Save action.
  4. On repaired code, verify that unsupported metadata is ignored, legitimate attribution still renders, adjacent date and secondary-ID cases stay usable, and Save plus reload preserves the record.

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.

The browser evidence establishes behavior for the controlled malformed metadata and supported sources. It does not establish a normal upstream path that produces this object, a security compromise or prototype pollution.

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-METADATA-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.