Nuxt Ollama integrates the official Ollama JavaScript library into Nuxt applications

Why it is Amber

• CVSS 7.5 high
• Remotely exploitable without logging in
• On your watchlist: ollama

References

• https://github.com/thoda-dev/nuxt-ollama/commit/156e813783ef322ee10dbbdd6bf446a449e1a04f
• https://github.com/thoda-dev/nuxt-ollama/releases/tag/v1.3.1
• https://github.com/thoda-dev/nuxt-ollama/security/advisories/GHSA-fxg7-897c-57mp

Original description

Nuxt Ollama integrates the official Ollama JavaScript library into Nuxt applications. Prior to 1.3.1, `src/module.ts` unconditionally merges all module options, including a configured cloud `api_key`, into `runtimeConfig.public.ollama`. Nuxt serializes this public configuration into the server-rendered HTML `window.__NUXT__` payload, exposing the API key in plaintext to any unauthenticated client that fetches a page. `src/runtime/composables/useOllama.ts` also reads the public key and sends it as an `Authorization` `Bearer` credential in browser-side Ollama requests. Following the documented cloud configuration is sufficient; the visible application template need not make an Ollama request for the secret to leak. A stolen key permits unauthorized cloud API requests at the operator's expense, quota or rate-limit exhaustion, and access to stored models or conversations if the key grants those permissions. This issue is fixed in version 1.3.1.