renovate[bot]
commented
2 weeks ago ℹ Artifact update notice
File name: go.mod
In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):
- 29 additional dependencies were updated
Details:
| Package | Change |
|---|---|
github.com/aws/aws-sdk-go-v2 |
v1.27.0 -> v1.28.0 |
github.com/aws/aws-sdk-go-v2/config |
v1.27.16 -> v1.27.19 |
github.com/aws/aws-sdk-go-v2/credentials |
v1.17.16 -> v1.17.19 |
github.com/aws/aws-sdk-go-v2/feature/ec2/imds |
v1.16.3 -> v1.16.6 |
github.com/aws/aws-sdk-go-v2/feature/s3/manager |
v1.16.21 -> v1.16.25 |
github.com/aws/aws-sdk-go-v2/internal/configsources |
v1.3.7 -> v1.3.10 |
github.com/aws/aws-sdk-go-v2/internal/endpoints/v2 |
v2.6.7 -> v2.6.10 |
github.com/aws/aws-sdk-go-v2/internal/v4a |
v1.3.7 -> v1.3.10 |
github.com/aws/aws-sdk-go-v2/service/internal/checksum |
v1.3.9 -> v1.3.12 |
github.com/aws/aws-sdk-go-v2/service/internal/presigned-url |
v1.11.9 -> v1.11.12 |
github.com/aws/aws-sdk-go-v2/service/internal/s3shared |
v1.17.7 -> v1.17.10 |
github.com/aws/aws-sdk-go-v2/service/s3 |
v1.54.3 -> v1.55.2 |
github.com/aws/aws-sdk-go-v2/service/sso |
v1.20.9 -> v1.20.12 |
github.com/aws/aws-sdk-go-v2/service/ssooidc |
v1.24.3 -> v1.24.6 |
github.com/aws/aws-sdk-go-v2/service/sts |
v1.28.10 -> v1.28.13 |
github.com/spf13/cobra |
v1.8.0 -> v1.8.1 |
golang.org/x/crypto |
v0.23.0 -> v0.24.0 |
golang.org/x/image |
v0.16.0 -> v0.17.0 |
golang.org/x/net |
v0.25.0 -> v0.26.0 |
golang.org/x/oauth2 |
v0.20.0 -> v0.21.0 |
golang.org/x/sys |
v0.20.0 -> v0.21.0 |
golang.org/x/term |
v0.20.0 -> v0.21.0 |
golang.org/x/text |
v0.15.0 -> v0.16.0 |
google.golang.org/api |
v0.182.0 -> v0.184.0 |
google.golang.org/genproto |
v0.0.0-20240528184218-531527333157 -> v0.0.0-20240604185151-ef581f913117 |
google.golang.org/genproto/googleapis/rpc |
v0.0.0-20240528184218-531527333157 -> v0.0.0-20240617180043-68d350f18fd4 |
google.golang.org/protobuf |
v1.34.1 -> v1.34.2 |
modernc.org/libc |
v1.51.0 -> v1.53.3 |
modernc.org/sqlite |
v1.30.0 -> v1.30.1 |
This PR contains the following updates:
v0.22.13->v0.22.14Release Notes
pocketbase/pocketbase (github.com/pocketbase/pocketbase)
### [`v0.22.14`](https://togithub.com/pocketbase/pocketbase/blob/HEAD/CHANGELOG.md#v02214) [Compare Source](https://togithub.com/pocketbase/pocketbase/compare/v0.22.13...v0.22.14) - Added OAuth2 POST redirect support (in case of `response_mode=form_post`) to allow specifying scopes for the Apple OAuth2 integration. Note 1: If you are using the "Manual code exchange" flow with Apple (aka. `authWithOAuth2Code()`), you need to either update your custom redirect handler to accept POST requests OR if you want to keep the old behavior and don't need the Apple user's email - replace in the Apple authorization url `response_mode=form_post` back to `response_mode=query`. Note 2: Existing users that have already logged in with Apple may need to revoke their access in order to see the email sharing options as shown in [this screenshot](https://togithub.com/pocketbase/pocketbase/discussions/5074#discussioncomment-9801855). If you want to force the new consent screen you could register a new Apple OAuth2 app. - ⚠️ Fixed a security vulnerability related to the OAuth2 email autolinking (thanks to D.Urness for reporting it). Just to be safe I've also published a [GitHub security advisory](https://togithub.com/pocketbase/pocketbase/security/advisories/GHSA-m93w-4fxv-r35v) (*may take some time to show up in the related security databases*). In order to be exploited you must have **both** OAuth2 and Password auth methods enabled. A possible attack scenario could be: - a malicious actor register with the targeted user's email (it is unverified) - at some later point in time the targeted user stumble on your app and decides to sign-up with OAuth2 (*this step could be also initiated by the attacker by sending an invite email to the targeted user*) - on successful OAuth2 auth we search for an existing PocketBase user matching with the OAuth2 user's email and associate them - because we haven't changed the password of the existing PocketBase user during the linking, the malicious actor has access to the targeted user account and will be able to login with the initially created email/password To prevent this for happening we now reset the password for this specific case if the previously created user wasn't verified (an exception to this is if the linking is explicit/manual, aka. when you send `Authorization:TOKEN` with the OAuth2 auth call). Additionally to warn users we now send an email alert in case the user has logged in with password but has at least one OAuth2 account linked. It looks something like: *Hello, Just to let you know that someone has logged in to your Acme account using a password while you already have OAuth2 GitLab auth linked. If you have recently signed in with a password, you may disregard this email. **If you don't recognize the above action, you should immediately change your Acme account password.** Thanks, Acme team* The flow will be further improved with the [ongoing refactoring](https://togithub.com/pocketbase/pocketbase/discussions/4355) and we will start sending emails for "unrecognized device" logins (OTP and MFA is already implemented and will be available with the next v0.23.0 release in the near future).Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.