sqlparse 0.6.1 fixes two flaws as maintainers end the project
Original title: sqlparse 0.6.1 fixes two vulnerabilities, announces EOL
A GitHub discussion says a flood of security reports influenced the decision to end sqlparse after this release.
Alan Coopersmith forwarded the sqlparse 0.6.1 changelog on the oss-security list. The changelog says the release fixes two vulnerabilities, and the project has announced it will end. A linked GitHub discussion describes how the volume of incoming security reports affected that decision. The post does not describe the bugs.
Unconfirmed: The post does not name the two vulnerabilities, their impact, or any CVE identifiers.
- The note was posted to oss-security on November 10.
- No CVE identifiers or affected version ranges appear in the post.
- GitHub discussion 945 covers the report volume behind the end-of-life decision.
| Product | Affected | Fixed in |
|---|---|---|
| sqlparse | — | 0.6.1 |
- 1.Upgrade to sqlparse 0.6.1.
- 2.Plan a replacement because the project is ending.
- Products
- sqlparse
From the original article
Posted by Alan Coopersmith on Nov 10 https://github. com/andialbrecht/sqlparse/blob/master/CHANGELOG says: https://github. com/andialbrecht/sqlparse/discussions/945 discusses how the flood of incoming security reports impacted the decision to end the project.
seclists.org
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.