# CVE-2018-1103: Openshift Enterprise source-to-image vulnerable to Arbitrary File Write via Archive Extraction (Zip Slip)

> An attacker can trick a user into copying files from a pod to override files outside the target directory via improper input validation.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 12 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-w55j-f7vx-6q37, GO-2020-0026

## What is CVE-2018-1103?

CVE-2018-1103 is a medium-severity path traversal vulnerability in Openshift Enterprise unsanitized paths in tar.go, published on 12 Jun 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Openshift Enterprise source-to-image before version 1.1.10 is vulnerable to an improper validation of user input. An attacker who could trick a user into using the command to copy files locally, from a pod, could override files outside of the target directory of the command.

Weakness: CWE-20 (Improper Input Validation), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2018-1103?

3 open source packages ship an affected version, including github.com/openshift/source-to-image. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/openshift/source-to-image` | Go | All versions | 1.1.10-0.20180427153919-f5cbcbc5cc6f |
| `github.com/openshift/source-to-image` | Go | All versions | 1.1.10-0.20180427153919-f5cbcbc5cc6f |
| `github.com/openshift/source-to-image` | Go | All versions | 1.1.10-0.20180427153919-f5cbcbc5cc6f |

Products: Redhat Source-to-Image.

## How do I fix CVE-2018-1103?

Upgrade github.com/openshift/source-to-image to 1.1.10-0.20180427153919-f5cbcbc5cc6f or later.

## Is CVE-2018-1103 being exploited?

There is no known exploitation of CVE-2018-1103 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1103 and fix it if it is affected.

What it is: CVE-2018-1103 is a medium-severity path traversal vulnerability in Openshift Enterprise unsanitized paths in tar.go, published on 12 Jun 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-1103 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/openshift/source-to-image (Go): affected all versions; fixed in 1.1.10-0.20180427153919-f5cbcbc5cc6f
- github.com/openshift/source-to-image (Go): affected all versions; fixed in 1.1.10-0.20180427153919-f5cbcbc5cc6f
- github.com/openshift/source-to-image (Go): affected all versions; fixed in 1.1.10-0.20180427153919-f5cbcbc5cc6f

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-1103/ (Markdown: https://insights.sbomify.com/CVE-2018-1103/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-1103
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-1103
- OSV: https://osv.dev/vulnerability/CVE-2018-1103

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-1103/
Summaries are generated and may contain mistakes; the official description above is the record.