Langfuse Slack OAuth Installation Endpoint Lacks Authentication, Enabling Arbitrary Project Linking
Langfuse is an open source large language model engineering platform. In versions 3.146.0 and below, the /api/public/slack/install endpoint initiates Slack OAuth using a projectId provided by the client without authentication or authorization. The projectId is preserved throughout the OAuth flow, and the callback stores installations based on this untrusted metadata. This allows an attacker to bind their Slack workspace to any project and potentially receive changes to prompts stored in Langfuse Prompt Management. An attacker can replace existing Prompt Slack Automation integrations or pre-register a malicious one, though the latter requires an authenticated user to unknowingly configure it despite visible workspace and channel indicators in the UI. This issue has been fixed in version 3.147.0.
References
- https://github.com/langfuse/langfuse/commit/3adc89e4d72729eabef55e46888b8ce80a7e3b0a x_refsource_MISC
- https://github.com/langfuse/langfuse/releases/tag/v3.147.0 x_refsource_MISC
- https://langfuse.com/docs/prompt-management/features/webhooks-slack-integrations x_refsource_MISC
- https://github.com/langfuse/langfuse/security/advisories/GHSA-pvq7-vvfj-p98x x_refsource_CONFIRM
Affected products
- ==>= 3.89.0, < 3.147.0
Matching in nixpkgs
pkgs.python312Packages.langfuse
Instrument your LLM app with decorators or low-level SDK and get detailed tracing/observability
pkgs.python313Packages.langfuse
Instrument your LLM app with decorators or low-level SDK and get detailed tracing/observability
Package maintainers
-
@natsukium Tomoya Otabi <nixpkgs@natsukium.com>