🇰🇷 한글 설명
패키지 관리가 활성화된 경우, Pulsar Functions 워커가 패키지 URL에 대한 권한을 요청자의 권한이 아닌 워커 자신의 권한으로 확인하는 취약점이 발견되었습니다. 이로 인해 인증된 사용자가 자신의 네임스페이스 권한을 이용해 다른 테넌트의 패키지 내용을 탈취할 수 있습니다. 노출된 패키지에는 애플리케이션 코드, 비즈니스 로직 또는 임베디드 자격 증명이 포함될 수 있습니다.
💡 쉬운 설명
권한 확인 과정에서 사용자가 아닌 시스템(워커)의 권한을 사용하기 때문에 발생하는 보안 허점입니다. 이를 통해 공격자는 허가되지 않은 다른 사용자의 패키지 파일을 몰래 읽어올 수 있습니다.
🇺🇸 원문 (English)
When package management is enabled, Pulsar Functions, Sources and Sinks can be registered or updated from a package stored in the Pulsar Packages Management Service by supplying a package URL. The Pulsar Functions worker authorized these requests only against the namespace in which the component was being registered or updated. It did not check whether the requesting user was permitted to access packages in the namespace that the package URL refers to, and it retrieved the package from the broker using the worker's own credentials. The permission check of the Packages Management Service was therefore applied to the worker's identity instead of the requesting user's. Package URLs of transform functions supplied when registering or updating a sink were handled in the same way.
An authenticated user who is permitted to register or update functions, sources or sinks in any namespace of their own tenant could use this to obtain the contents of a package stored in a namespace of another tenant, without having the packages permission on that namespace. The impact is limited to disclosure of package contents, which may include application code, business logic or embedded credentials. The issue does not allow packages to be modified or deleted and does not affect availability.
This issue only affects deployments that have authentication and authorization enabled and in which package management has been enabled: the broker setting enablePackagesManagement and, in current releases, the functions worker setting functionsWorkerEnablePackageManagement. Both settings are disabled by default.
This issue affects Apache Pulsar versions from 2.8.0 before 4.0.14, from 4.1.0 through 4.1.3, and from 4.2.0 before 4.2.5.
- 4.0.x version users should upgrade to at least 4.0.14.
- 4.1.x and 4.2.x version users should upgrade to at least 4.2.5.
Users operating versions prior to those listed above should upgrade to the aforementioned patched versions or newer versions.
The currently supported Apache Pulsar release lines are 4.0.x and 5.0.x. The supported versions schedule is available at https://pulsar.apache.org/contribute/release-policy/.
📍 영향받는 시스템
Apache Pulsar 2.8.0 ~ 4.0.13, 4.1.0 ~ 4.1.3, 4.2.0 ~ 4.2.4
⚔️ 공격 벡터
인증된 사용자가 타 테넌트의 패키지 URL을 포함하여 함수/소스/싱크를 등록 또는 업데이트 요청
🛡️ 대응 방법
Apache Pulsar를 4.0.14, 4.1.4(또는 4.2.5 이상) 버전으로 업그레이드하십시오.
🔧 검증 코드
출력된 버전이 취약한 버전 범위(2.8.0~4.0.13, 4.1.0~4.1.3, 4.2.0~4.2.4)에 해당하는지 확인하십시오.
💻 영향받는 소프트웨어
IBM Verify Identity Access