Skip to content
Fencer Intel
high —

GHSA-jcjx-c3j3-44pr json

Insufficient Session Expiration in @cyyynthia/tokenize

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 A bug introduced in version 1.1.0 made Tokenize generate faulty tokens with NaN as a generation date. As a result, tokens would not properly expire and remain valid regardless of the `lastTokenReset` field.

### Patches Version 1.1.3 contains a patch that'll invalidate these faulty tokens and make new ones behave as expected.

### Workarounds None. Tokens do not hold the necessary information to perform invalidation anymore.

### References PR #1

### For more information If you have any questions or comments about this advisory: * Open an issue in [github.com/cyyynthia/tokenize](https://github.com/cyyynthia/tokenize) * Email us at [cynthia@cynthia.dev](mailto:cynthia@cynthia.dev)

Patch / fix

  • npm @cyyynthia/tokenize 1.1.3

Is GHSA-jcjx-c3j3-44pr 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 @cyyynthia/tokenize
>=1.1.0, <1.1.3
1.1.3

Classification

Weakness
  • CWE-613 DEPRECATED: Insufficient Session Expiration

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.