CVE-2023-36607
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 are missing authorization for running some API commands. An attacker running these commands could reveal sensitive information such as software versions and web server file contents.
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 lack proper authorization checks on certain API endpoints, allowing unauthenticated attackers to execute specific API commands that expose sensitive system information including software versions and web server file contents.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 device as an Ovarro TBox RTUExamine the device or its network documentation to confirm it is an Ovarro TBox model from the affected product line (Ms Cpu32, Ms Cpu32 S2, Lt2, Tg2, or Rm2).Affected if The device is one of the listed Ovarro TBox models.
-
Determine the firmware versionAccess the device's web interface or use its administrative console to retrieve the installed firmware version. Compare the version number against the affected range <= 1.50.598.Affected if The firmware version is 1.50.598 or lower.
-
Check for exposed API endpointsAttempt to access the device's web API endpoints without providing authentication credentials. Observe whether the device returns sensitive system information such as software versions or file contents.Affected if The API endpoints respond to unauthenticated requests with sensitive system data.
-
Verify API authorization behaviorSend API requests to known endpoints (such as those that expose version or file information) without an active session or API key. Inspect the HTTP response for success codes and returned data.Affected if Unauthenticated API requests successfully return sensitive information that should require authorization.
A system is affected if it is an Ovarro TBox RTU running firmware version 1.50.598 or lower AND its API endpoints are accessible without authentication, allowing exposure of sensitive system information.
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 dataImplement role-based access control and authorization validation on all API endpoints to ensure only authenticated and authorized users can access sensitive system information.
- Consultation8.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-36607 — 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-36607 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