Nixpkgs security tracker
7.6 HIGH
- CVSS version (CVSS): 3.1
- Attack Vector (AV): Network (N)
- Attack Complexity (AC): Low (L)
- Privileges Required (PR): High (H)
- User Interaction (UI): None (N)
- Scope (S): Changed (C)
- Confidentiality (C): High (H)
- Integrity (I): Low (L)
- Availability (A): None (N)
- Modified Attack Vector (MAV): Network (N)
- Modified Attack Complexity (MAC): Low (L)
- Modified Privileges Required (MPR): High (H)
- Modified User Interaction (MUI): None (N)
- Modified Confidentiality (MC): High (H)
- Modified Scope (MS): Changed (C)
- Modified Integrity (MI): Low (L)
- Modified Availability (MA): None (N)
by @LeSuisse Activity log
- Created suggestion
- @LeSuisse accepted
- @LeSuisse published on GitHub
Prowler: Server-Side Request Forgery (SSRF) in Lighthouse Provider
Prowler is a cloud security platform. Prior to 5.33.1, an authenticated user with Lighthouse provider configuration access could supply an unvalidated base_url for the openai_compatible provider through POST /api/v1/lighthouse/providers and POST /api/v1/lighthouse/providers/{id}/connection, causing api/src/backend/tasks/jobs/lighthouse_providers.py to send outbound requests, including the API key in the Authorization header, to attacker-controlled or internal endpoints when client.models.list was called. This issue is fixed in version 5.33.1.
References
-
https://github.com/prowler-cloud/prowler/security/advisories/GHSA-fhj4-q47f-w7mv x_refsource_CONFIRMexploit
-
https://github.com/prowler-cloud/prowler/pull/11928 x_refsource_MISC
-
https://github.com/prowler-cloud/prowler/pull/11940 x_refsource_MISC
-
https://github.com/prowler-cloud/prowler/releases/tag/5.33.1 x_refsource_MISC
-
https://github.com/prowler-cloud/prowler/releases/tag/5.34.0 x_refsource_MISC
Affected products
- ==< 5.33.1
Package maintainers
-
@fabaff Fabian Affolter <mail@fabian-affolter.ch>
9.9 CRITICAL
- CVSS version (CVSS): 3.1
- Attack Vector (AV): Network (N)
- Attack Complexity (AC): Low (L)
- Privileges Required (PR): Low (L)
- User Interaction (UI): None (N)
- Scope (S): Changed (C)
- Confidentiality (C): High (H)
- Integrity (I): High (H)
- Availability (A): High (H)
- Modified Attack Vector (MAV): Network (N)
- Modified Attack Complexity (MAC): Low (L)
- Modified Privileges Required (MPR): Low (L)
- Modified User Interaction (MUI): None (N)
- Modified Confidentiality (MC): High (H)
- Modified Scope (MS): Changed (C)
- Modified Integrity (MI): High (H)
- Modified Availability (MA): High (H)
by @LeSuisse Activity log
- Created suggestion
- @LeSuisse accepted
- @LeSuisse published on GitHub
Prowler: RCE on Prowler App workers via kubeconfig auth-provider cmd-path
Prowler is a cloud security platform. Prior to 5.36.0, the Kubernetes provider connection test accepted kubeconfig_content containing a legacy gcp auth-provider with config.cmd-path and config.cmd-args because kubeconfig_contains_exec_auth in api/src/backend/api/v1/serializers.py checked only exec blocks, and POST /api/v1/providers/{id}/connection loaded it through config.load_kube_config_from_dict in prowler/providers/kubernetes/kubernetes_provider.py, causing kubernetes-python CommandTokenSource.token to run the attacker-supplied command through subprocess.Popen on the shared worker. This issue is fixed in version 5.36.0.
References
-
https://github.com/prowler-cloud/prowler/security/advisories/GHSA-ccqh-6cjc-wp4j x_refsource_CONFIRMexploit
-
https://github.com/prowler-cloud/prowler/pull/12091 x_refsource_MISC
-
https://github.com/prowler-cloud/prowler/releases/tag/5.36.0 x_refsource_MISC
Affected products
- ==< 5.36.0
Package maintainers
-
@fabaff Fabian Affolter <mail@fabian-affolter.ch>