CVE-2023-36608
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 · uneditedThe affected TBox RTUs store hashed passwords using MD5 encryption, which is an insecure encryption algorithm.
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 confidenceTBox RTUs store user passwords using MD5 hashing, which is cryptographically weak and vulnerable to rainbow table attacks and collision attacks. An attacker with access to the password hashes could potentially recover plaintext passwords.
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>= 1.46, <= 1.50.598>= 1.46, <= 1.50.598>= 1.46, <= 1.50.598>= 1.46, <= 1.50.598>= 1.46, <= 1.50.598CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 TBox device modelAccess the device management interface or check system information files (e.g., /proc/cpuinfo, device configuration files) to determine the exact model variant (Ms Cpu32, Ms Cpu32 S2, Lt2, Tg2, or Rm2)Affected if The model is one of the affected variants (Ms Cpu32, Ms Cpu32 S2, Lt2, Tg2, or Rm2)
-
Check the installed firmware versionUse the device's web interface, CLI, or check firmware version files (typically found in /version, /etc/version, or via 'show version' command) to obtain the exact firmware version numberAffected if The firmware version falls within the range >= 1.46 and <= 1.50.598
-
Locate password storage configurationExamine the device configuration files where user credentials are stored. These may be in files such as user.cfg, passwd, users.xml, or similar configuration files in the /config, /etc, or data partitionsAffected if Password configuration files exist on the device
-
Inspect password hash formatOpen the password storage file identified in the previous step and examine the format of stored password hashes. Look for 32-character hexadecimal strings (typical MD5 length)Affected if Stored passwords appear as 32-character hex strings characteristic of MD5 hashes
-
Verify hashing algorithm usedIf possible, compare a known plaintext password against its stored hash using MD5 verification (e.g., use md5sum command or hashlib in Python). Also examine any system files or documentation that may indicate the hashing algorithmAffected if The stored hashes are confirmed to be MD5 digests of plaintext passwords
The environment is affected if the device is an Ovarro TBox model (Ms Cpu32, Ms Cpu32 S2, Lt2, Tg2, or Rm2) running firmware version 1.46 through 1.50.598 that stores user passwords as MD5 hashes.
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 dataMigrate password storage to a modern password hashing algorithm such as bcrypt, scrypt, or Argon2 with appropriate work factors, and implement a secure password migration path for existing users.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-36608 — 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-2023-36608 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