CVE-2023-45321
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 Android Client application, when enrolled with the define method 1 (the user manually inserts the server ip address), use HTTP protocol to retrieve sensitive information (ip address and credentials to connect to a remote MQTT broker entity) instead of HTTPS and this feature is not configurable by the user. Due to the lack of encryption of HTTP,this issue allows an attacker placed in the same subnet network of the HMI device to intercept username and password necessary to authenticate to the MQTT server responsible to implement the remote management protocol.
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 Android Client application for HMI devices uses unencrypted HTTP to fetch sensitive MQTT broker credentials (IP address, username, password) during enrollment when users manually input the server IP. An attacker on the same network segment can intercept these credentials via plaintext traffic sniffing, enabling unauthorized MQTT broker access.
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 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/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 the HMI device modelLocate the device model number on the physical device or check the system information in the Ctrlx HMI web interface. Confirm it is one of: WR2107, WR2110, or WR2115.Affected if The device model is a Boschrexroth Ctrlx Hmi Web Panel WR2107, WR2110, or WR2115 - all versions of these models are affected.
-
Verify enrollment uses HTTP for credential transferDuring the manual server IP enrollment process, use a network packet capture tool (such as Wireshark or tcpdump) on the network segment to observe the traffic when the device fetches MQTT broker credentials. Look for plaintext HTTP requests on port 80.Affected if HTTP (port 80) traffic is observed in plain text during enrollment, or the device makes requests to an http:// URL rather than https://.
-
Check web interface enrollment URL schemeAccess the Ctrlx HMI web interface enrollment configuration screen. Look for the server address input field and inspect what protocol (http/https) is displayed or configured for the MQTT broker connection.Affected if The enrollment interface shows or accepts an HTTP URL scheme for the MQTT broker server address.
-
Inspect network logs for plaintext credentialsReview any available device logs, network gateway logs, or proxy logs that capture traffic from the HMI device during enrollment. Search for plaintext transmission of IP addresses, usernames, or passwords.Affected if Credentials are transmitted in plaintext or logged in plain text during the enrollment process.
If the device is a Ctrlx HMI Web Panel WR2107, WR2110, or WR2115 and the enrollment process transmits MQTT broker credentials over unencrypted HTTP, the environment is affected by this vulnerability.
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 dataReplace HTTP with HTTPS for credential retrieval and implement proper certificate validation. Add user-configurable transport protocol selection or enforce HTTPS with fallback handling.
- 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-45321 — 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-45321 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