CVE-2021-37555
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 · uneditedTX9 Automatic Food Dispenser v3.2.57 devices allow access to a shell as root/superuser, a related issue to CVE-2019-16734. To connect, the telnet service is used on port 23 with the default password of 059AnkJ for the root account. The user can then download the filesystem through preinstalled BusyBox utilities (e.g., tar and nc).
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 TX9 Automatic Food Dispenser v3.2.57 contains a hardcoded default root password (059AnkJ) enabling unauthenticated telnet access on port 23. Attackers can gain root shell access and exfiltrate the entire filesystem using preinstalled BusyBox utilities (tar and nc).
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= 3.2.57CVSS 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 the device model and firmware versionCheck the device label, web interface, or administrative panel for the model name (Trixie Tx9 Automatic Food Dispenser) and firmware version (look for 3.2.57)Affected if The device is a Trixie Tx9 Automatic Food Dispenser running firmware version 3.2.57
-
Verify telnet service is exposedScan the device or network for open port 23 (telnet) using nmap or netcat: nmap -p 23 <device-ip> or nc -zv <device-ip> 23Affected if Port 23/telnet is open and reachable on the device
-
Check if default root password is activeAttempt to connect to telnet on port 23 using the hardcoded credential root:059AnkJ (note: this is an intrusive check that may trigger alerts or lockout)Affected if Authentication succeeds with username root and password 059AnkJ, granting root shell access
-
Confirm BusyBox utilities availabilityAfter telnet login, check for presence of tar and nc in the PATH or /bin directory: which tar; which nc or ls /bin/tar /bin/ncAffected if Both tar and nc utilities are available for filesystem exfiltration
A defender is affected if they operate a Trixie Tx9 Automatic Food Dispenser on firmware 3.2.57 with telnet port 23 exposed and the hardcoded root password (059AnkJ) still active.
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 dataImmediately change the default root password, disable telnet service if not required, and implement network segmentation or firewall rules to prevent unauthorized access to the telnet port.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-37555 — 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-37555 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