Skip to content
Fencer Intel
high —

GHSA-3r5h-5jcg-gmgg json

CPU Exhaustion via O(N^2) Regex Backtracking in sqlparse.utils.SPLIT_REGEX

published 13d ago modified 10d ago

Unreviewed: the maintainers' own advisory

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

Patch / fix

  • pypi sqlparse 0.6.1

Is GHSA-3r5h-5jcg-gmgg 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 sqlparse
<=0.6.0
0.6.1

Classification

Weakness
  • CWE-1333 Inefficient Regular Expression Complexity

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