🚀 Socket Launch Week Day 5:Introducing Repository Access Permissions and Custom Roles.Learn more
Sign In

@ai-sdk/google

Package Overview
Dependencies
Maintainers
3
Versions
527
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@ai-sdk/google - npm Package Compare versions

Comparing version
2.0.74
to
2.0.75
+14
-0
CHANGELOG.md
# @ai-sdk/google
## 2.0.75
### Patch Changes
- 9f67efe: fix: only send provider credentials to same-origin response-supplied URLs
Several provider clients followed a URL taken from the provider's API response (a polling/status URL or a final media URL such as `polling_url`, `urls.get`, `result_url`, `result.sample`, or `video.uri`) and reused the authenticated headers — or appended `?key=<API_KEY>` — on that request. Because the host of the response-supplied URL was never validated, the long-lived API key was sent to whatever host the response named (a CDN in the benign case, or an attacker-chosen host if the provider response was tampered with), allowing credential exfiltration.
A new `isSameOrigin` helper is added to `@ai-sdk/provider-utils`, and the affected fetches in `@ai-sdk/black-forest-labs`, `@ai-sdk/fireworks`, `@ai-sdk/replicate`, `@ai-sdk/gladia`, `@ai-sdk/fal`, and `@ai-sdk/google` now attach credentials only when the followed URL is same-origin with the provider's configured API origin. Requests to a foreign origin are made without the credential.
- Updated dependencies [9f67efe]
- Updated dependencies [eea9166]
- @ai-sdk/provider-utils@3.0.26
## 2.0.74

@@ -4,0 +18,0 @@

+2
-2
{
"name": "@ai-sdk/google",
"version": "2.0.74",
"version": "2.0.75",
"license": "Apache-2.0",

@@ -30,3 +30,3 @@ "sideEffects": false,

"@ai-sdk/provider": "2.0.3",
"@ai-sdk/provider-utils": "3.0.25"
"@ai-sdk/provider-utils": "3.0.26"
},

@@ -33,0 +33,0 @@ "devDependencies": {

Sorry, the diff of this file is too big to display

Sorry, the diff of this file is too big to display