Remote Code Execution in Baicells QRTB Platform
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.
- Published
- Feb 10, 2023
- Updated
- Jun 17, 2026
- EPSS
- 1.2% · 67th percentile
- CWE
- CWE-79
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
40
Plan
Add it to your regular patch cycle.
- CVSS
- 40 / 40 · 10.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 10.0
- CNA · Baicells
- 8.1
- 1.9 point gap
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| baicells | neutrino 430 firmware | cpe:2.3:o:baicells:neutrino_430_firmware |
| baicells | neutrino 430 | cpe:2.3:h:baicells:neutrino_430 |
| baicells | nova430l firmware | cpe:2.3:o:baicells:nova430l_firmware |
| baicells | nova430l | cpe:2.3:h:baicells:nova430l |
| baicells | nova430e firmware | cpe:2.3:o:baicells:nova430e_firmware |
| baicells | nova430e | cpe:2.3:h:baicells:nova430e |
| baicells | nova436q firmware | cpe:2.3:o:baicells:nova436q_firmware |
| baicells | nova436q | cpe:2.3:h:baicells:nova436q |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- baicells neutrino 430 firmwareup to qrtb_2.12.7 inclusive
- baicells nova430e firmwareup to qrtb_2.12.7 inclusive
- baicells nova430l firmwareup to qrtb_2.12.7 inclusive
- baicells nova436q firmwareup to qrtb_2.12.7 inclusive
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Baicells). Independent of NVD's CPE analysis and usually ahead of it.
Baicells Neutrino 430
- up to and including 2.12.7affected · patchfixed in 2.12.8
Baicells Nova 430E
- up to and including 2.12.7affected · patchfixed in 2.12.8
Baicells Nova 430I
- up to and including 2.12.7affected · patchfixed in 2.12.8
Baicells Nova 436Q
- up to and including 2.12.7affected · patchfixed in 2.12.8
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Baicells Neutrino 430 | 2.12.8 | Vendor (CNA) |
| Baicells Nova 430E | 2.12.8 | Vendor (CNA) |
| Baicells Nova 430I | 2.12.8 | Vendor (CNA) |
| Baicells Nova 436Q | 2.12.8 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Rustam Aminfinder
- Baicells Security Teamremediation developer
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
nvd-primary
Root cause
User content is inserted into the page as HTML. The browser interprets the content as code rather than data.
The bug in code
The whole CWE-79 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
commentEl.innerHTML = comment.body;Fixed
commentEl.textContent = comment.body;Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.