For your digest
golang.org/x/crypto: Improper Verification of Cryptographic Signature in golang.org/x/crypto
It touches something Phylax follows. No evidence of use yet.
Does it affect what I run?
golang.org/x/crypto (Go)
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- golang.org/x/crypto (Go): every version, before 0.0.0-20200220183623-bac4c82f6975
- golang.org/x/crypto (Go): every version, before 0.0.0-20200220183623-bac4c82f6975
The fix
golang.org/x/crypto (Go) fixed in 0.0.0-20200220183623-bac4c82f6975
gogo get golang.org/x/crypto@v0.0.0-20200220183623-bac4c82f6975Check what is installedgo list -m golang.org/x/cryptoPaste into Cursor, Lovable or Claude CodeUpgrade the Go dependency golang.org/x/crypto to 0.0.0-20200220183623-bac4c82f6975 or the nearest later release, to fix CVE-2020-9283. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
No evidence that it is being used, or can be. It is listed because of what it affects.
Timeline
- First published here, as "For your digest".