Joker linter executed project-local .jokerd/linter.* files during linting
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| candid82 | joker | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Candid82 | Joker |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-m835-3cm9-rggg | Joker linter executed project-local .jokerd/linter.* files during linting |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.162% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Candid82
Candid82 joker |
|
| Vendors & Products |
Candid82
Candid82 joker |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Joker is a small Clojure interpreter, linter and formatter written in Go. Prior to 1.8.2, `joker --lint <file>` walks upward from the linted file to locate a `.jokerd/` directory and executes matching `linter.*` files before linting. Those files contain executable Joker/Clojure code, so linting a file inside an untrusted repository can execute repository-supplied code with the linter user's privileges. Editor integrations and CI jobs that automatically lint checked-out source can trigger this behavior. The patch stops executing project-local linter customizations and loads executable customization only from the user's home directory. This issue is fixed in version 1.8.2. | |
| Title | Joker linter executed project-local .jokerd/linter.* files during linting | |
| Weaknesses | CWE-829 | |
| References |
| |
| Metrics |
cvssV3_1
|