dbcve.org
Neutrino 430 FirmwareOperating system · Baicells

CVE-2023-0776

CRITICAL · 10.0 CVSS v3.1 Published 2023-02-11
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 · unedited
Baicells Nova 436Q, Nova 430E, Nova 430I, and Neutrino 430 LTE TDD eNodeB devices with firmware through QRTB 2.12.7 are vulnerable to remote shell code exploitation via HTTP command injections. Commands are executed using pre-login execution and executed with root permissions. The following methods below have been tested and validated by a 3rd party analyst and has been confirmed exploitable special thanks to Rustam Amin for providing the steps to reproduce. 

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 confidence

This is a pre-authentication command injection vulnerability in Baicells Nova and Neutrino LTE TDD eNodeB devices running firmware through QRTB 2.12.7. Attackers can inject arbitrary shell commands via HTTP requests that are executed with root privileges before any login, resulting in full remote code execution as root.

MitigationUpdate firmware to a version beyond QRTB 2.12.7 when available from Baicells; if no patch exists, restrict network access to the device management interface using firewall rules or network segmentation.

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
Neutrino 430 FirmwareOperating system
Affected:<= qrtb_2.12.7
Nova430l FirmwareOperating system
Affected:<= qrtb_2.12.7
Nova430e FirmwareOperating system
Affected:<= qrtb_2.12.7
Nova436q FirmwareOperating system
Affected:<= qrtb_2.12.7

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Baicells device model
    Access the device web interface or check the device label to determine if the model is one of: Neutrino 430, Nova430l, Nova430e, or Nova436q. This can also be retrieved via SNMP or by logging into the device via SSH and running 'cat /proc/cpuinfo' or checking the web UI login page source.
    Affected if The device model is Neutrino 430, Nova430l, Nova430e, or Nova436q.
  2. Check the installed firmware version
    Log into the device web UI and navigate to the System or Status page to view the firmware version, or use SSH to run 'cat /proc/version' or check the file containing version info typically found in the web interface or via SNMP OID. Look specifically for the QRTB version number.
    Affected if The firmware version shows QRTB 2.12.7 or earlier (any version <= qrtb_2.12.7).
  3. Verify HTTP management interface accessibility
    Attempt to access the device HTTP/HTTPS management interface from an external network location, or check firewall rules and network segmentation configuration to determine if ports 80/443 are exposed to untrusted networks.
    Affected if The HTTP management interface is reachable from an untrusted network (such as the internet or an untrusted VLAN).

The device is affected if it is a Baicells Neutrino 430, Nova430l, Nova430e, or Nova436q model running firmware QRTB version 2.12.7 or earlier, and its management interface is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch baicells.com →
Interim mitigation

Update firmware to a version beyond QRTB 2.12.7 when available from Baicells; if no patch exists, restrict network access to the device management interface using firewall rules or network segmentation.

Recommended fix Moderate confidence

Latest firmware version available at baicells.com/Service/Firmware newer than qrtb_2.12.7

  1. 1. Navigate to the Baicells firmware download page at https://baicells.com/Service/Firmware
  2. 2. Locate the firmware update for your specific device model (Neutrino 430, Nova430l, Nova430e, or Nova436q)
  3. 3. Download the latest available firmware version that is newer than qrtb_2.12.7
  4. 4. Consult the device's firmware upgrade instructions documentation
  5. 5. Apply the firmware update following the vendor's recommended procedure
  6. 6. After upgrade, verify the vulnerability is no longer present
Caveat Review Baicells release notes for any compatibility or configuration changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Neutrino 430 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-0776 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-0776 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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