Skip to content
Fencer Intel
medium —

GHSA-f7q5-7cq5-gvgh json

Empty PATH entry causes interpreter discovery to execute a file from the current directory

published last mo. modified last mo.

Unreviewed: the maintainers' own advisory

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

Patch / fix

  • pypi python-discovery 1.6.1

Is GHSA-f7q5-7cq5-gvgh 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
pypi python-discovery
<=1.6.0
1.6.1

Classification

Weakness
  • CWE-427 Uncontrolled Search Path Element

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