-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x/vulndb: potential Go vuln in github.com/aws/aws-sdk-go/service/s3/s3crypto: GHSA-f5pg-7wfw-84q9 #646
Comments
Change https://go.dev/cl/423994 mentions this issue: |
For #646 Change-Id: Icd46b0f5a83bec71e6601ee0c8ef4251d7e10b62 Reviewed-on: https://go-review.googlesource.com/c/vulndb/+/423994 Reviewed-by: Damien Neil <dneil@google.com> Reviewed-by: Julie Qiu <julieqiu@google.com>
Change https://go.dev/cl/427335 mentions this issue: |
There are two separate GHSAs describing AWS S3 Crypto SDK vulnerabilities that, while technically different, have a common underlying effect: An attacker with write access to an S3 bucket can read files in that bucket. (One vulnerability allows decrypting files using AES-CBC. The other allows converting a file using AES-GCM with the KMS option to use AES-CBC, at which point the first vulnerability can be used to decrypt it.) This vulnerability is fixed in the new EncryptionClientV2 API. Users of the old EncryptionClient API remain vulnerable, even when using newer versions of the github.com/aws/aws-sdk-go module Update this report to describe the impact (attacker can decrypt your files, but only if they have write access), the mitigation (switch APIs), and to mark the V1 API vulnerable at all module versions. Fixes #635. Fixes #646. Change-Id: Ifd1e26119f40808977a1265f192e60fd199b1763 Reviewed-on: https://go-review.googlesource.com/c/vulndb/+/427335 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Roland Shoemaker <roland@golang.org> Run-TryBot: Damien Neil <dneil@google.com>
Change https://go.dev/cl/629377 mentions this issue: |
Add fixed version. - data/reports/GO-2022-0646.yaml Fixes #3276 Updates #646 Change-Id: Ic76152e6070a28c0e865306ccd488061e15fb789 Reviewed-on: https://go-review.googlesource.com/c/vulndb/+/629377 Reviewed-by: Zvonimir Pavlinovic <zpavlinovic@google.com> Auto-Submit: Tatiana Bradley <tatianabradley@google.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Change https://go.dev/cl/635736 mentions this issue: |
Change https://go.dev/cl/635282 mentions this issue: |
Restore historical published version that was accidentally deleted in a previous CL. (This happened because we changed the way we handle published times). - data/reports/GO-2022-0646.yaml Updates #646 Change-Id: Ib02681c69e3b805eae705a3baffede8cc3bc358f Reviewed-on: https://go-review.googlesource.com/c/vulndb/+/635282 Reviewed-by: Ian Cottrell <iancottrell@google.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
In GitHub Security Advisory GHSA-f5pg-7wfw-84q9, there is a vulnerability in the following Go packages or modules:
See doc/triage.md for instructions on how to triage this report.
The text was updated successfully, but these errors were encountered: