CVE-2021-45877
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMultiple 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe GARO Wallbox GLB/GTB/GTC devices contain hardcoded credentials stored in /etc/tomcat8/tomcat-user.xml. This allows unauthenticated attackers to access the Tomcat manager interface on port 8000 and gain full control of the Tomcat application server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 185<= 185<= 185CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify device model and firmware versionAccess the device admin interface or check the device label/metadata to confirm it is a GARO Wallbox GLB, GTB, or GTC model. Note the installed firmware version.Affected if The device is a GARO Wallbox GLB, GTB, or GTC with firmware version 185 or lower.
-
Locate the tomcat-user.xml fileAttempt to access the file at /etc/tomcat8/tomcat-user.xml on the device file system, or extract the firmware image and search for this file path.Affected if The file /etc/tomcat8/tomcat-user.xml exists in the device firmware or file system.
-
Inspect for hardcoded credentialsOpen the tomcat-user.xml file and examine the <user> elements for usernames and passwords. Look for static, non-variable credential entries.Affected if The file contains <user> entries with hardcoded password attributes that are not dynamically generated or unique per device.
-
Check Tomcat manager accessibilityAttempt to access the Tomcat manager interface by navigating to http://<device-ip>:8000/manager/html from an external host, or verify port 8000 is listening and exposed on the device network interface.Affected if The Tomcat manager interface on port 8000 is accessible from an untrusted network without authentication.
A user is affected if they own a GARO Wallbox GLB, GTB, or GTC device running firmware version 185 or lower, and the device exposes the Tomcat manager interface on port 8000 with hardcoded credentials present in /etc/tomcat8/tomcat-user.xml.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRemove or replace the hardcoded credentials in tomcat-user.xml, implement dynamic credential management, and coordinate with the vendor for firmware updates if the hardcoded credentials are embedded in the firmware image.
- Consultation8.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-45877 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-45877 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data