Skip to content
Fencer Intel
critical —

GHSA-ccv5-c45x-2q38 json

Unauthenticated remote code execution in Taskcluster web-server via sift library

published 5mo ago modified 5mo ago

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository taskcluster/taskcluster. 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
—
not scored
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 taskcluster/taskcluster: the maintainers' own advisory, not a reviewed GitHub Advisory Database entry. The full advisory is on GitHub.

Is GHSA-ccv5-c45x-2q38 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

Classification

Weakness
  • CWE-20 Improper Input Validation
  • CWE-94 Improper Control of Generation of Code
  • CWE-95 Improper Neutralization of Directives in Dynamically Evaluated Code
  • CWE-250 Execution with Unnecessary Privileges
  • CWE-306 Missing Authentication for Critical Functionality

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 taskcluster/taskcluster published their own advisory on GitHub. Its facts and headline are shown here; the description stays on GitHub.