Redocly CLI: Path traversal when using `split` command
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Redocly | redocly-cli | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Redocly | Redoc |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-657c-g7qc-r9j2 | Redocly CLI: Path traversal when using `split` command |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.179% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Redocly
Redocly redoc |
|
| Vendors & Products |
Redocly
Redocly redoc |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Redocly CLI makes OpenAPI validation, linting, and documentation workflows easier. Prior to @redocly/cli 2.33.2, the split command constructs output paths under --outDir from untrusted OpenAPI or AsyncAPI component names and x-codeSamples lang values without verifying that the resolved target remains inside the selected directory. A description containing literal ../ traversal segments in those fields can cause the split command to place or overwrite files outside --outDir. Component data remains constrained to YAML or JSON, and code-sample filenames remain based on the HTTP method, so this is not an unrestricted arbitrary-content file write. This issue is fixed in @redocly/cli version 2.33.2. | |
| Title | Redocly CLI: Path traversal when using `split` command | |
| Weaknesses | CWE-22 CWE-73 |
|
| References |
|
|
| Metrics |
cvssV3_1
|