Summary
Etherpad addressed weak token RNG, login timing, plugin path handling, API request handling
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 usecrypto.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.timingSafeEqualplus 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/2merged all request headers into the API field set. Now forwards onlyauthorization, matching the openapi.ts handler. - Pad-creation side effect:
API.appendChatMessagecould create arbitrary pads (missinggetPadSafe). Now requires the pad to exist. - Error info disclosure (CWE-209): the admin file server echoed filesystem error detail; now returns a generic message.
Impact
Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-92HR-GMR6-H8CP? GHSA-92HR-GMR6-H8CP is a medium-severity path traversal vulnerability in ep_etherpad-lite (npm), affecting versions <= 1.8.14. It is fixed in 3.3.0. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
- Which versions of ep_etherpad-lite are affected by GHSA-92HR-GMR6-H8CP? ep_etherpad-lite (npm) versions <= 1.8.14 is affected.
- Is there a fix for GHSA-92HR-GMR6-H8CP? Yes. GHSA-92HR-GMR6-H8CP is fixed in 3.3.0. Upgrade to this version or later.
- Is GHSA-92HR-GMR6-H8CP exploitable, and should I be worried? Whether GHSA-92HR-GMR6-H8CP is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-92HR-GMR6-H8CP is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-92HR-GMR6-H8CP? Upgrade
ep_etherpad-liteto 3.3.0 or later.