FunctionToString overflows on cyclic Proxy prototype chains

Aperta
  • Qualcosa non va?
#25,963 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

  • #25964 di @chiliec — chiusa senza merge

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
javascript, typescript
Ambito
devtools

Direzione di ricerca

Start with functionToStringIntegration and packages/core/src/utils/object.ts, focusing on how getOriginalFunction reads __sentry_original__. Use the reproduction in the issue to investigate the cyclic Proxy case; done means the wrapped toString returns normally for that case without changing native behavior.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Browser Bug

The patched Function.prototype.toString from functionToStringIntegration throws RangeError: Maximum call stack size exceeded for a function whose prototype chain loops back through a Proxy. Native toString returns normally for the same function. Anti-tamper and fingerprinting scripts use this kind of probe to detect patched natives.

Reported by Sergio Lombana from a customer on @sentry/[email protected] with Castle bot detection loaded. Their event has a short stack: the Sentry toString wrapper is the top frame and the frames below it are Castle's.

Root cause (high confidence for the repro, unverified for the customer's exact trigger)

The wrapper calls getOriginalFunction(this), which reads this.__sentry_original__ (packages/core/src/utils/object.ts). For a function without that own property, the read walks the prototype chain. If the chain loops back through a Proxy, the walk never ends and overflows inside the wrapper frame. Native toString never reads properties from this, so it doesn't overflow.

This still happens on develop after #25921 / #25922. Those PRs fixed the apply re-entry and huge-argument-list overflows, not this property lookup.

Reproduction

const orig = Function.prototype.toString;
const callOrig = Function.prototype.call.bind(orig);

function f() {}
Object.setPrototypeOf(f, Object.create(new Proxy(f, {})));

Function.prototype.toString.call(f); // native: 'function f() {}'

// same shape as the current wrapper on develop
Function.prototype.toString = function () {
  const o = this.__sentry_original__;
  return callOrig(o ?? this);
};

Function.prototype.toString.call(f); // RangeError: Maximum call stack size exceeded

Unknowns

  • Someone else reproduced this artificial case but couldn't trigger the error with the same Castle and SDK versions. So it's not confirmed that this is the probe Castle runs in the customer's environment.

Workaround

  • Filter the RangeError via ignoreErrors / beforeSend. Removing functionToStringIntegration can make Sentry-wrapped functions look tampered to anti-bot scripts, so it isn't recommended here.

Related: #21965, #22515, #25921, #25922

via Sergio.

--

View Session [Sentry]

Lingua principale
TypeScript
Stelle
8.8k
Fork
1.9k
Merge medio
1g 21h
PR unite (30g)
617

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di getsentry/sentry-javascript

Tutte le issue di getsentry/sentry-javascript

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.