CVE-2023-36611
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 allow low privilege users to access software security tokens of higher privilege. This could allow an attacker with “user” privileges to access files requiring higher privileges by establishing an SSH session and providing the other tokens.
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 · moderate confidenceTBox RTUs have a privilege escalation vulnerability where low-privilege users can access security tokens intended for higher-privilege users. By establishing an SSH session and providing tokens belonging to higher-privilege users, an attacker can bypass authorization checks and access files or functions requiring elevated privileges.
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.50.598<= 1.50.598<= 1.50.598<= 1.50.598<= 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 TBox device firmware versionAccess the TBox management interface (web UI, console, or vendor management tool) and locate the firmware version information. Compare the installed version against the affected range.Affected if The firmware version is 1.50.598 or any lower version number.
-
Confirm SSH access is enabledVerify whether the SSH service is running and accessible on the TBox device. Check the device network configuration or services list.Affected if SSH is enabled and accessible, providing the attack vector for token misuse.
-
Review user account privilege assignmentsList all user accounts configured on the TBox and their assigned privilege levels. Identify accounts with elevated privileges versus standard users.Affected if Multiple privilege levels exist and lower-privilege users can authenticate via SSH.
-
Audit SSH authentication logsExamine SSH access logs or authentication records on the TBox for sessions using security tokens. Look for patterns where standard users may have authenticated with elevated-level tokens.Affected if Logs show SSH sessions where low-privilege accounts used tokens associated with higher-privilege roles.
A TBox device is affected if it runs firmware version 1.50.598 or lower, has SSH access enabled, and contains user accounts with different privilege levels that could be exploited for token-based privilege escalation.
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 dataApply vendor-supplied patches for TBox RTUs that properly validate security token privileges and enforce strict authorization boundaries. Until patched, monitor SSH access logs for anomalous token usage patterns.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-36611 — 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-36611 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