CVE-2023-23545
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 · uneditedMissing authentication for critical function exists in T&D Corporation and ESPEC MIC CORP. data logger products, which may allow a remote unauthenticated attacker to alter the product settings without authentication. Affected products and versions are as follows: T&D Corporation data logger products (TR-71W/72W all firmware versions, RTR-5W all firmware versions, WDR-7 all firmware versions, WDR-3 all firmware versions, and WS-2 all firmware versions), and ESPEC MIC CORP. data logger products (RT-12N/RS-12N all firmware versions, RT-22BN all firmware versions, and TEU-12N all firmware versions).
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 confidenceMissing authentication for critical function in T&D and ESPEC MIC data loggers allows remote unauthenticated attackers to alter device settings. The vulnerability affects multiple model families across both vendors with all firmware versions impacted, enabling settings manipulation without any credentials.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 T&D or ESPEC MIC data loggers on the networkScan network for devices matching model names: Tr 71w, Tr 72w, Rtr 5w, Wdr 7, Wdr 3, Ws 2 (T&D) or Rt 12n, Rs 12n (Especmic). Check device HTTP server banners, MAC OUI lookups for vendor identifiers, or consult network device inventories.Affected if Any of the listed model families are present on the network.
-
Determine if management interface is network-accessibleCheck firewall rules, ACLs, or network segmentation to see if the data logger web interface (typically HTTP/HTTPS on ports 80/443 or custom ports) is reachable from untrusted network segments or the internet.Affected if The device management interface is exposed to untrusted networks or the internet.
-
Verify authentication is required for settings accessAttempt to access the device configuration or settings endpoints (such as parameter change pages, setup wizards, or admin functions) without providing any credentials. Observe whether access is granted or redirected to a login page.Affected if Settings or configuration pages load without requiring any username or password.
-
Check for unauthenticated configuration modification capabilityIf settings are accessible without auth, attempt to submit a benign configuration change (such as altering a display or logging interval) to confirm the critical function lacks authentication enforcement.Affected if Configuration parameters can be modified without any authentication token, session, or credential.
If any T&D Tr/Rtr/Wdr/Ws or ESPEC MIC Rt/Rs data loggers are network-accessible with their management interface reachable from untrusted networks, and critical settings can be viewed or modified without authentication, the environment is affected by this CVE.
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 network segmentation to isolate data loggers from untrusted networks, restrict exposure to management interfaces via firewall rules, and monitor for unauthorized configuration changes. Contact T&D and ESPEC MIC for available firmware updates or security patches.
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23545 — 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-23545 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