# CVE-2020-2077: Information disclosure in SICK Package Analytics

> Unauthorized attackers can read sensitive data via the REST API due to incorrect default permissions in SICK Package Analytics.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jul 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-24pm-ccpf-9wgw

## What is CVE-2020-2077?

CVE-2020-2077 is a high-severity vulnerability in SICK Package Analytics, published on 29 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SICK Package Analytics software up to and including version V04.0.0 are vulnerable due to incorrect default permissions settings. An unauthorized attacker could read sensitive data from the system by querying for known files using the REST API directly.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


Products: Sick Package Analytics.

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

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

## Is CVE-2020-2077 being exploited?

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

## Other vulnerabilities in SICK Package Analytics

- [CVE-2020-2076](https://insights.sbomify.com/CVE-2020-2076/): Auth bypass in SICK Package Analytics (critical 9.8)
- [CVE-2020-2078](https://insights.sbomify.com/CVE-2020-2078/): Hardcoded credentials in SICK Package Analytics (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-2077 is a high-severity vulnerability in SICK Package Analytics, published on 29 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-2077 in the wild and no public exploit code.

Affected product: SICK Package Analytics. 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-2077/ (Markdown: https://insights.sbomify.com/CVE-2020-2077/index.md)
```

## Sources

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

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