CVE-2023-1748
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 listed versions of Nexx Smart Home devices use hard-coded credentials. An attacker with unauthenticated access to the Nexx Home mobile application or the affected firmware could view the credentials and access the MQ Telemetry Server (MQTT) server and the ability to remotely control garage doors or smart plugs for any customer.
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 confidenceHard-coded credentials in Nexx Smart Home devices (firmware and mobile app) allow unauthenticated attackers to access the MQTT server and remotely control garage doors or smart plugs for any customer. The credentials are embedded in the firmware and mobile application, enabling complete unauthenticated access to the IoT infrastructure.
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<= nxal100v-p1-9-1<= nxg100bv-p3-4-1<= nxpg100cv4-0-0<= nxg200v-p3-4-1CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 Nexx device models on your networkScan your network for devices with model identifiers Nxal 100, Nxg 100b, Nxpg 100w, or Nxg 200. Check device labels, DHCP lease tables, or network scan results for these model names.Affected if Any of these four device models are present on the network
-
Check firmware version against affected releasesAccess the device admin interface or use the manufacturer app to retrieve the firmware version. Compare it to the affected versions: nxal100v-p1-9-1 or lower, nxg100bv-p3-4-1 or lower, nxpg100cv4-0-0 or lower, or nxg200v-p3-4-1 or lower.Affected if The installed firmware version is equal to or below any of the listed affected versions for your device model
-
Confirm MQTT connectivity is enabledMonitor network traffic or check device settings to determine if the device communicates with an MQTT broker on port 1883 or 8883 (TLS). Look for MQTT protocol traffic in your network logs.Affected if MQTT communication is active between the device and a broker, indicating the hard-coded credentials could be exploited
You are affected if you have any Nexx Nxal 100, Nxg 100b, Nxpg 100w, or Nxg 200 devices running firmware at or below the specified version limits and those devices use MQTT connectivity.
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 hard-coded credentials with secure, unique per-device credentials or certificate-based authentication; deploy firmware updates to all affected devices; update the mobile application to remove embedded credentials; implement proper authentication on the MQTT server.
- Consultation12.0 h
- Implementation32.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $19,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-1748 — 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-1748 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