Dependencies: Pin SQLitePCLRaw.lib.e_sqlite3 to a non-vulnerable version (closes #23325) - #23393
Conversation
|
Claude finished @AndyButland's task in 1m 32s —— View job PR ReviewTarget: Pins the transitive No issues found. The change:
ApprovedThis looks good to be merged as-is, but please do a manual sanity check and testing before merging. |
There was a problem hiding this comment.
Pull request overview
Pins the transitive NuGet dependency SQLitePCLRaw.lib.e_sqlite3 to a non-vulnerable version via Central Package Management, preventing resolution to the vulnerable 2.1.11 while upstream packages still reference bundle_e_sqlite3 2.1.11.
Changes:
- Adds a transitive pin for
SQLitePCLRaw.lib.e_sqlite3to2.1.12inDirectory.Packages.props. - Documents the rationale and advisory reference inline alongside other transitive pins.
|



Description
SQLitePCLRaw.lib.e_sqlite3was resolving to the vulnerable2.1.11(GHSA-2m69-gcr7-jv3q, high severity). It is a purely transitive dependency, reached viaMicrosoft.Data.Sqlite(used byUmbraco.Cms.Persistence.Sqlite) andMicrosoft.EntityFrameworkCore.Sqlite(used by the EF Core persistence projects), both of which pull it in throughSQLitePCLRaw.bundle_e_sqlite3.SQLitePCLRaw.lib.e_sqlite3has been patched in2.1.12and we've run all Umbraco integration tests on this version, which pass (as CI on this PR should confirm).I was waiting a few days for our direct dependencies to pin their versions on 2.1.12. However as yet they haven't. The latest available versions of those direct dependencies (
Microsoft.Data.Sqlite/Microsoft.EntityFrameworkCore.Sqlite10.0.10), released two days ago, still referencebundle_e_sqlite3 2.1.11, so there is no upstream floor bump to adopt yet.As such, I think we'll need to pin Umbraco instead so we ship referencing a non-vulnerable version and avioid the build warnings.
This pins the transitive
SQLitePCLRaw.lib.e_sqlite3forward to the patched2.1.12inDirectory.Packages.props, following the existing convention for transitive pinned versions. Only the nativelib.e_sqlite3package is flagged, so it is the sole package pinned.Fixes #23325.
Testing
Solution should build and CI checks pass.