# CVE-2020-36628: Calsign APDE ZIP File CopyBuildTask.java handleExtract path traversal

> A path traversal vulnerability in APDE allows attackers to read or modify files outside the intended directory via crafted ZIP archives.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Dec 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-5hrp-9f94-jhqh

## What is CVE-2020-36628?

CVE-2020-36628 is a medium-severity path traversal vulnerability in Calsign APDE, published on 25 Dec 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability classified as critical has been found in Calsign APDE. This affects the function handleExtract of the file APDE/src/main/java/com/calsignlabs/apde/build/dag/CopyBuildTask.java of the component ZIP File Handler. The manipulation leads to path traversal. Upgrading to version 0.5.2-pre2-alpha is able to address this issue. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-216747.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2020-36628?

It affects 1 product.


Products: Android Processing Development Environment Project Android Processing Development Environment.

## How do I fix CVE-2020-36628?

No fix has been published for CVE-2020-36628 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-36628 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-36628 and fix it if it is affected.

What it is: CVE-2020-36628 is a medium-severity path traversal vulnerability in Calsign APDE, published on 25 Dec 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-36628 in the wild and no public exploit code.

Affected product: Calsign APDE. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2020-36628/ (Markdown: https://insights.sbomify.com/CVE-2020-36628/index.md)
```

## Sources

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

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