dbcve.org
Rtd FirmwareOperating system · Baicells

CVE-2023-24508

CRITICAL · 9.6 CVSS v3.1 Published 2023-01-26
Fix available
A fix is available. Upgrade to 3.7.11.6 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

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 227, Nova 233, and Nova 243 LTE TDD eNodeB and Nova 246 devices with firmware through RTS/RTD 3.6.6 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

Baicells Nova 227, 233, 243, and 246 LTE TDD eNodeB devices running firmware through RTS/RTD 3.6.6 contain a pre-authentication HTTP command injection vulnerability that allows remote attackers to execute arbitrary shell code with root privileges.

MitigationUpgrade to firmware version newer than RTS/RTD 3.6.6. If patching is not immediately possible, restrict network access to management interfaces and implement compensating controls such as network segmentation and WAF rules to block suspicious HTTP requests.

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
Rtd FirmwareOperating system
Affected:< 3.7.11.6
Rts FirmwareOperating system
Affected:< 3.7.11.6

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
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 management interface or use SNMP to query the hardware model. Look for Nova 227, Nova 233, Nova 243, or Nova 246 in the device information page or SNMP OID sysDescr.
    Affected if The device model is Baicells Nova 227, 233, 243, or 246
  2. Determine the firmware version
    In the device web UI, navigate to the Status or System Information page to view the firmware version. Alternatively, query via SNMP or check the kernel boot log for the RTS/RTD version string.
    Affected if The firmware version displayed is lower than 3.7.11.6, or the version shows RTS/RTD 3.6.6 or earlier
  3. Verify HTTP management interface exposure
    Check network configuration or firewall rules to determine if TCP port 80 or 443 (HTTP/HTTPS management) is accessible from untrusted networks. Use a port scanner or check the device ACL settings.
    Affected if The HTTP management interface is reachable from external or untrusted network segments without network segmentation in place

The device is affected if it is a Baicells Nova 227/233/243/246 running RTS or RTD firmware version lower than 3.7.11.6, and the HTTP 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
Upgrade available Upgrade to 3.7.11.6 or later
Fixed in 3.7.11.6
Interim mitigation

Upgrade to firmware version newer than RTS/RTD 3.6.6. If patching is not immediately possible, restrict network access to management interfaces and implement compensating controls such as network segmentation and WAF rules to block suspicious HTTP requests.

Recommended fix Moderate confidence

RTS/RTD firmware version 3.7.11.6

  1. Upgrade the RTS or RTD firmware to version 3.7.11.6 or later to remediate this vulnerability
  2. Verify the upgrade was successful by checking the firmware version in the device management interface
  3. After upgrading, confirm that the HTTP command injection vulnerability is no longer exploitable

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

Fix this in Rtd Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-24508 — 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-24508 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