# CVE-2020-6020: Command injection in ICA Management Portal

> A trusted administrator can execute arbitrary commands or crash the system via weak input validation in the Internal CA web management interface.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-j4c7-wg39-qp3p

## What is CVE-2020-6020?

CVE-2020-6020 is a medium-severity command injection vulnerability in ICA Management Portal, published on 24 Sep 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Check Point Security Management's Internal CA web management before Jumbo HFAs R80.10 Take 278, R80.20 Take 160, R80.30 Take 210, and R80.40 Take 38, can be manipulated to run commands as a high privileged user or crash, due to weak input validation on inputs by a trusted management administrator.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Checkpoint Ica Management Portal.

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

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

## Is CVE-2020-6020 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-6020 is a medium-severity command injection vulnerability in ICA Management Portal, published on 24 Sep 2020. 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-6020 in the wild and no public exploit code.

Affected product: ICA Management Portal. 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-6020/ (Markdown: https://insights.sbomify.com/CVE-2020-6020/index.md)
```

## Sources

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

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