Skipper arbitrary code execution through lua filters
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| zalando | skipper | affected |
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Zalando | Skipper | — |
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-cc8m-98fm-rc9g | Skipper is vulnerable to arbitrary code execution through lua filters |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.514% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:zalando:skipper:*:*:*:*:*:*:*:* |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Zalando
Zalando skipper |
|
| Vendors & Products |
Zalando
Zalando skipper |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Skipper is an HTTP router and reverse proxy for service composition. The default skipper configuration before 0.23.0 was -lua-sources=inline,file. The problem starts if untrusted users can create lua filters, because of -lua-sources=inline , for example through a Kubernetes Ingress resource. The configuration inline allows these user to create a script that is able to read the filesystem accessible to the skipper process and if the user has access to read the logs, they an read skipper secrets. This vulnerability is fixed in 0.23.0. | |
| Title | Skipper arbitrary code execution through lua filters | |
| Weaknesses | CWE-250 CWE-522 CWE-94 |
|
| References |
| |
| Metrics |
cvssV3_1
|