CVE-2023-31446 is a critical command injection flaw, scored 9.8, in Cassia Networks XC1000 and XC2000 Bluetooth gateway firmware. An unsanitized queueUrl setting reaches a root level command on startup. A researcher write-up says firmware 2.1.1.230720 fixes it, so update and require API authentication.
What's affected
The NVD record, dated 2024-01-10, says that in Cassia Gateway firmware XC1000_2.1.1.2303082218 and XC2000_2.1.1.2303090947, the queueUrl parameter in /bypass/config is not sanitized, which leads to injecting Bash code and executing it with root privileges on device startup. The weakness is CWE-77 (command injection). The vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
The vendor site fetched for this post is a general product page and has no advisory. The version detail comes from a third party write-up on the KSCSC blog, which was published by the researchers who reported the flaw. It states the affected firmware as earlier than 2.1.1.230309, says the vendor confirmed the issue, and gives 2.1.1.230720 as the patched version. The write-up also says the endpoint is not authenticated by default and that the feature was not in Cassia's official documentation.
The sources differ slightly. NVD lists two exact build strings, while the write-up uses a broader earlier-than range. Treat anything below 2.1.1.230720 as suspect until Cassia confirms otherwise.
How to check if you're exposed
Find the firmware version of each gateway in its management interface or through your IoT management system and compare it with 2.1.1.230720. Do the same for both XC1000 and XC2000 models.
Check whether the gateway management API is reachable from networks it should not be. The write-up says access to the endpoint is unauthenticated by default, so reachability matters as much as the version. A gateway on a flat network or exposed to the internet is the worst case.
Ask Cassia support for its own advisory and the exact fixed build for your hardware, because this post could not confirm those from a vendor page.
What to do now
- Inventory all Cassia gateways and record model and firmware version.
- Update to the patched firmware, 2.1.1.230720 or later, and confirm with Cassia.
- Enable and require API authentication where your version supports it, as the write-up advises.
- Put gateways on a segmented network and block management access from untrusted networks.
- Monitor traffic to the gateway API and review the device configuration for settings you did not make, especially any queue or cloud push settings.
Why it matters
CWE-77 appears when text from a request is placed into a command without cleaning it. Here the setting is saved, then read at boot by a service running as root, so one unauthenticated write can become code execution with full control of the device after a restart.
Gateways bridge Bluetooth sensors to company networks, so a compromised unit can expose data and act as a foothold inside the network. The record is not in the CISA Known Exploited Vulnerabilities catalog and no source we fetched reports active use. A public write-up exists, which is a reason to patch sooner. Safeguard offers a free in-browser dependency scan at gold.safeguard.sh/scan for the packages in your own code. It does not inspect installed desktop tools or device firmware, so those need a manual inventory.
Quick check
Is this exploited in the wild?
The record shows kev as false and no fetched source reports exploitation. A public write-up exists, so patch promptly.
Which firmware fixes it?
The researcher write-up names 2.1.1.230720 as patched. Confirm the exact build with Cassia, since no vendor advisory was available to fetch.
Sources
Last reviewed: 19 October 2026.