🇰🇷 한글 설명
livebook-dev의 Livebook Teams 인증 과정에서 CSRF 취약점이 발견되었습니다. 공격자가 생성한 인증 코드를 피해자가 실행하도록 유도하면, 피해자의 브라우저 세션이 공격자의 계정으로 연결되어 데이터 유출 및 작업 결과 노출이 발생할 수 있습니다.
💡 쉬운 설명
사용자가 자신도 모르게 공격자의 계정으로 로그인하게 만드는 공격입니다. 사용자가 작업한 중요한 정보나 데이터가 사용자의 계정이 아닌 공격자의 계정으로 저장되어 공격자가 이를 볼 수 있게 됩니다.
🇺🇸 원문 (English)
Cross-Site Request Forgery (CSRF) vulnerability in livebook-dev livebook allows an attacker to authenticate a victim's browser session under the attacker's own Livebook Teams identity.
When Livebook is configured to use Livebook Teams for identity, Livebook.ZTA.LivebookTeams.handle_request/4 in lib/livebook/zta/livebook_teams.ex handles the OAuth-style callback carrying a teams_identity marker and a code parameter. The clause exchanges that code for an access token and writes the token into the browser session without verifying any value that ties the callback to the browser session that started the login. No state or nonce is generated when the flow is initiated: Livebook.Teams.Requests.create_auth_request/1 in lib/livebook/teams/requests.ex sends an empty request body, so no per-attempt value is ever registered, and the callback clause has nothing to compare against.
An attacker who holds membership in the same Livebook Teams organisation as the target instance can therefore begin the login flow themselves, retain the resulting authorization code without redeeming it, and induce a victim to open a crafted URL carrying that code. The victim's browser completes the exchange and the resulting session is bound to the attacker's identity rather than the victim's. The victim is not required to hold any particular privilege, and no credential belonging to the victim is involved. The vulnerability does not allow the attacker to authenticate as the victim.
The consequence is that a user believes they are working in their own authenticated session while they are in fact operating as another identity. Work performed in that session is attributed to the attacker's account, and secrets, uploaded data, or notebook results the victim produces are exposed to the attacker rather than kept in the victim's own account. The authorization code must be redeemed within a short window after the login flow begins, which constrains the timing of the attack but not its feasibility.
This issue affects livebook: from 0.15.0 before 0.18.7 and from 0.19.0 before 0.19.9.
📍 영향받는 시스템
livebook: 0.15.0 ~ 0.18.6, 0.19.0 ~ 0.19.8
⚔️ 공격 벡터
공격자가 생성한 OAuth 인증 코드가 포함된 악성 URL을 피해자가 클릭하도록 유도
🛡️ 대응 방법
Livebook 버전을 0.18.7 또는 0.19.9 이상으로 업데이트
🔧 검증 코드
명령어 실행 결과에 취약한 버전 범위가 출력되면 해당 시스템은 보안 업데이트가 필요한 상태입니다.
mix exec 'Mix.Task.run(["version"])' 2>/dev/null | grep -E '0\.(15\.|18\.(0|1|2|3|4|5|6)|19\.(0|1|2|3|4|5|6|7|8))'
📊 CVSS Vector String
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
💻 영향받는 소프트웨어
IBM Security Verify Access