# CVE-2020-25507: Misconfiguration in n/a

> Local attackers can execute arbitrary code as root or twcloud due to insecure file permissions set during installation.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 28 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-66pq-mwg2-mc6q

## What is CVE-2020-25507?

CVE-2020-25507 is a high-severity vulnerability in n/a, published on 28 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An incorrect permission assignment during the installation script of TeamworkCloud 18.0 thru 19.0 allows a local unprivileged attacker to execute arbitrary code as root. During installation, the user is instructed to set the system enviroment file with world writable permissions (0777 /etc/environment). Any local unprivileged user can execute arbitrary code simply by writing to /etc/environment, which will force all users, including root, to execute arbitrary code during the next login or reboot. In addition, the entire home directory of the twcloud user at /home/twcloud is recursively given world writable permissions. This allows any local unprivileged attacker to execute arbitrary code, as twcloud. This product was previous named Cameo Enterprise Data Warehouse (CEDW).

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 1 product.


Products: 3ds Teamwork Cloud.

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

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

## Is CVE-2020-25507 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-25507 is a high-severity vulnerability in n/a, published on 28 Dec 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-25507 in the wild and no public exploit code.

Affected product: n/a. 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-25507/ (Markdown: https://insights.sbomify.com/CVE-2020-25507/index.md)
```

## Sources

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

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