Skip to content
Fencer Intel
high —

GHSA-4g53-vp7q-gfjv json

constructEvent does not verify header

published 5y ago modified 5y ago

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### Impact Anyone verifying a Stripe webhook request via this library's `constructEvent` function.

### Patches Upgrade to 1.1.4.

### Workarounds Use `await verifyHeader(...)` directly instead of `constructEvent`.

### References https://github.com/worker-tools/stripe-webhook/issues/1

Patch / fix

  • npm @worker-tools/stripe-webhook 1.1.4

Is GHSA-4g53-vp7q-gfjv in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
npm @worker-tools/stripe-webhook
<1.1.4
1.1.4

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.