# CVE-2021-45877: Hardcoded credentials in n/a

> Hardcoded credentials in GARO Wallbox allow attackers to gain full control of the Tomcat manager interface.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Mar 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-7jm2-v68f-ww8p

## What is CVE-2021-45877?

CVE-2021-45877 is a critical vulnerability in n/a, published on 21 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple versions of GARO Wallbox GLB/GTB/GTC are affected by hard coded credentials. A hardcoded credential exist in /etc/tomcat8/tomcat-user.xml, which allows attackers to gain authorized access and control the tomcat completely on port 8000 in the tomcat manger page.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2021-45877?

It affects 3 products.


Products: Garo Wallbox Glb Firmware, Garo Wallbox Gtb Firmware, Garo Wallbox Gtc Firmware.

## How do I fix CVE-2021-45877?

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

## Is CVE-2021-45877 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-45876](https://insights.sbomify.com/CVE-2021-45876/): Command injection in n/a (critical 9.8)
- [CVE-2021-45878](https://insights.sbomify.com/CVE-2021-45878/): Missing authorization in n/a (critical 9.1)
- [CVE-2023-30399](https://insights.sbomify.com/CVE-2023-30399/): Open redirect in n/a (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-45877 and fix it if it is affected.

What it is: CVE-2021-45877 is a critical vulnerability in n/a, published on 21 Mar 2022. 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-2021-45877 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-2021-45877/ (Markdown: https://insights.sbomify.com/CVE-2021-45877/index.md)
```

## Sources

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

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