Bgs5 FirmwareOperating system · Telit

CVE-2023-47610

CRITICAL · 9.8 CVSS v3.1 Published 2023-11-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
A CWE-120: Buffer Copy without Checking Size of Input vulnerability exists in Telit Cinterion EHS5/6/8 that could allow a remote unauthenticated attacker to execute arbitrary code on the targeted system by sending a specially crafted SMS message.

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 · moderate confidence

A buffer overflow vulnerability (CWE-120) in Telit Cinterion EHS5/6/8 cellular IoT modems allows remote unauthenticated attackers to achieve arbitrary code execution via specially crafted SMS messages. The vulnerability stems from insufficient bounds checking when parsing incoming SMS data, enabling an attacker to overflow a buffer and inject malicious code without authentication.

MitigationApply vendor-supplied firmware patches for the EHS5/6/8 devices; until patches are available, consider network segmentation to restrict SMS traffic or disable SMS processing if not required for the device's function.

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
Bgs5 FirmwareOperating system
Affected:all versions
Ehs5 FirmwareOperating system
Affected:all versions
Ehs6 FirmwareOperating system
Affected:all versions
Ehs8 FirmwareOperating system
Affected:all versions
Pds5 FirmwareOperating system
Affected:all versions
Pds6 FirmwareOperating system
Affected:all versions
Pds8 FirmwareOperating system
Affected:all versions
Els61 FirmwareOperating system
Affected:all versions

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 Telit modem models in your environment
    Review device inventories, hardware asset lists, or network documentation to locate any Telit Cinterion cellular IoT modems. Check for model numbers Bgs5, Ehs5, Ehs6, Ehs8, Pds5, Pds6, Pds8, or Els61.
    Affected if Any of these eight model numbers are present in your environment, as all firmware versions are affected.
  2. Confirm SMS functionality is enabled on affected modems
    Access the modem's AT command interface or management interface and check SMS-related AT commands such as AT+CNMI (New Message Indications) or AT+CSMS (Message Service). A configuration that processes incoming SMS messages indicates SMS is enabled.
    Affected if SMS message processing is enabled on the device, as the buffer overflow occurs during SMS parsing.
  3. Check modem's SMS receiving configuration
    Query the modem using AT+CNMI to see how incoming SMS messages are handled. Look for settings that direct SMS to memory (such as AT+CNMI=1,1 or similar) which indicates active SMS processing.
    Affected if The modem is configured to receive and store SMS messages, making it vulnerable to specially crafted SMS attacks.
  4. Assess network exposure to external SMS traffic
    Review network architecture to determine if the cellular interface can receive SMS from external sources. Check if SMS traffic is filtered, blocked, or segmented from untrusted networks.
    Affected if The modem's cellular interface can receive SMS messages from external/untrusted sources without filtering.

You are affected if any Telit Bgs5, Ehs5, Ehs6, Ehs8, Pds5, Pds6, Pds8, or Els61 modems in your environment have SMS processing enabled and can receive external SMS traffic.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware patches for the EHS5/6/8 devices; until patches are available, consider network segmentation to restrict SMS traffic or disable SMS processing if not required for the device's function.

Fix this in Bgs5 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-47610 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