Skip to content
Fencer Intel
high 7.5

GHSA-65rr-73jq-6qhf json

CLI login reactivates a revoked Personal Access Token

published 23d ago modified 23d ago

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository triggerdotdev/trigger.dev. GitHub has not reviewed it into the GitHub Advisory Database and no CVE record has reached us yet, so everything here comes from the maintainers alone. Read the full advisory on GitHub.

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

Summary

Security advisory published by the maintainers of triggerdotdev/trigger.dev: the maintainers' own advisory, not a reviewed GitHub Advisory Database entry. The full advisory is on GitHub.

Is GHSA-65rr-73jq-6qhf in your stack? 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

CVSS scores

assigned by version score vector
the maintainers 3.1 7.5 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Classification

Weakness
  • CWE-346 Origin Validation Error
  • CWE-451 User Interface (UI) Misrepresentation of Critical Information
  • CWE-613 DEPRECATED: Insufficient Session Expiration
  • CWE-1021 Improper Restriction of Rendered UI Layers or Frames

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.

The maintainers of triggerdotdev/trigger.dev published their own advisory on GitHub. Its facts and headline are shown here; the description stays on GitHub.