Skip to content
Fencer Intel
medium —

GHSA-92hr-gmr6-h8cp json

Etherpad addressed weak token RNG, login timing, plugin path handling, API request handling

published 2mo ago modified 2mo 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

Fix: PR #7906 (ether/etherpad). A set of medium/low hardening fixes:

- **Weak RNG for tokens (CWE-330):** author/session/readonly IDs were generated with `Math.random()` (client and server). Now use `crypto.getRandomValues`. - **Login timing / no failure delay (CWE-208/CWE-307):** the OIDC interaction login used a non-constant-time password compare with no failure delay. Now uses `crypto.timingSafeEqual` plus a uniform failure delay; user lookup is own-property only. - **Plugin dependency path handling (CWE-22):** plugin dependency names from package.json were used to build filesystem paths without validation (admin-gated install). Now validated against the npm name grammar. - **API parameter pollution (CWE-235):** `/api/2` merged all request headers into the API field set. Now forwards only `authorization`, matching the openapi.ts handler. - **Pad-creation side effect:** `API.appendChatMessage` could create arbitrary pads (missing `getPadSafe`). Now requires the pad to exist. - **Error info disclosure (CWE-209):** the admin file server echoed filesystem error detail; now returns a generic message.

Patch / fix

  • npm ep_etherpad-lite 3.3.0

Is GHSA-92hr-gmr6-h8cp 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 ep_etherpad-lite
<3.3.0
3.3.0

Classification

Weakness
  • CWE-208 Observable Timing Discrepancy
  • CWE-209 Generation of Error Message Containing Sensitive Information
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory
  • CWE-235 Improper Handling of Extra Parameters
  • CWE-330 Use of Insufficiently Random Values

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.