docs(security): ADR 0002 — accept pgx/v4 + pgproto3/v2 risk (no upstream fix)#120
Merged
Merged
Conversation
…eam fix) Documents dismissal of Dependabot alerts #23-#25 (pgproto3/v2 DoS, HIGH) and #54-#56 (pgx/v4 SQLi, low). Both packages are at their final vulnerable releases with no patch (fix only in pgx/v5); they are transitive via go-db-credential-refresh/driver v1.2.1 (RDS IAM cred rotation), which has not migrated to pgx/v5. Risk assessed tolerable (DoS needs malicious PG server; SQLi query pattern unused). Alerts dismissed as tolerable_risk with follow-up. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents the resolution of the 6 Dependabot alerts on pgx/v4 + pgproto3/v2.
These have no upstream fix — pgx/v4 (≤4.18.3) and pgproto3/v2 (≤2.3.3) are at their final vulnerable releases; the patch exists only in the pgx/v5 line. They are transitive via
go-db-credential-refresh/driverv1.2.1 (latest), used for AWS RDS IAM credential rotation, which has not migrated to pgx/v5.Risk assessed tolerable (pgproto3 DoS requires a malicious Postgres server — we connect only to trusted RDS; pgx SQLi placeholder pattern is not used). The 6 alerts (#23–#25 high, #54–#56 low) have been dismissed as tolerable_risk; this ADR records the reasoning and the follow-up to migrate when upstream adopts pgx/v5.
Doc-only.