CVE-2023-0052
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 · uneditedSAUTER Controls Nova 200–220 Series with firmware version 3.3-006 and prior and BACnetstac version 4.2.1 and prior allows the execution of commands without credentials. As Telnet and file transfer protocol (FTP) are the only protocols available for device management, an unauthorized user could access the system and modify the device configuration, which could result in the unauthorized user executing unrestricted malicious commands.
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 SAUTER Controls Nova 200–220 Series and BACnetstac contain a critical authentication bypass vulnerability. The devices use Telnet and FTP for management without requiring credentials, allowing any unauthenticated network attacker to connect directly to these services and execute arbitrary commands on the device with full 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<= 3.3-006<= 3.3-006<= 3.3-006<= 3.3-006<= 3.3-006CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 device model and firmware versionAccess the device web interface or use SNMP to query the device inventory. For command-line access, run 'show version' or equivalent command via the device console or management interface. Locate the firmware version string (e.g., Eyk220f001, Eyk230f001, Eyk300f001, Am300f001, Am300f002) and compare it to <= 3.3-006.Affected if The device model matches one of the affected product names (Nova 220, Nova 230, Nova 106, Modunet300) AND the firmware version is 3.3-006 or lower.
-
Confirm Telnet service is enabled and exposedFrom a trusted internal network host, attempt a telnet connection to the device IP address on port 23. Run: telnet <device_ip>. Observe whether the connection succeeds immediately without presenting a login prompt or requiring any credentials.Affected if The Telnet connection succeeds and provides shell or command access without prompting for any username or password.
-
Confirm FTP service is enabled and exposedFrom a trusted internal network host, attempt an FTP connection to the device IP address on port 21. Run: ftp <device_ip>. Observe whether the connection succeeds without requiring authentication credentials.Affected if The FTP connection succeeds and provides file system access or command execution without prompting for any username or password.
-
Check network accessibility of management portsPerform a port scan of the device IP address targeting ports 21 (FTP) and 23 (Telnet). Use: nmap -p 21,23 <device_ip>. Verify whether these ports are listening and reachable from the network.Affected if Ports 21 and/or 23 are open and reachable on the device, indicating the vulnerable services are exposed.
A device is affected if it is a SAUTER Controls Nova or Modunet300 model running firmware version 3.3-006 or lower AND has Telnet or FTP services accessible without authentication credentials.
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 dataIsolate affected devices on a restricted network segment with firewall rules blocking external Telnet/FTP access; contact SAUTER for firmware updates that address this authentication bypass and consider implementing compensating controls such as network segmentation until patches are available.
- Consultation8.0 h
- Implementation12.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 $8,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0052 — 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-0052 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