dbcve.org
Bgs5 FirmwareOperating system · Telit

CVE-2023-47613

HIGH · 7.1 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 →
73/100
Remediation priority · Elevated
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-23: Relative Path Traversal vulnerability exists in Telit Cinterion BGS5, Telit Cinterion EHS5/6/8, Telit Cinterion PDS5/6/8, Telit Cinterion ELS61/81, Telit Cinterion PLS62 that could allow a local, low privileged attacker to escape from virtual directories and get read/write access to protected files on the targeted system.

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 CWE-23 Relative Path Traversal vulnerability in Telit Cinterion cellular modem modules (BGS5, EHS5/6/8, PDS5/6/8, ELS61/81, PLS62) allows a local low-privileged attacker to escape configured virtual directories and gain unauthorized read/write access to protected filesystem locations outside the intended directory boundaries.

MitigationApply vendor-provided firmware patches from Telit to all affected modem modules; until patches are available, minimize local attack surface by restricting device access and network exposure, and consider network segmentation to limit exposure to local attackers.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

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 Cinterion modem modules in your environment
    Inventory all cellular modem hardware and look for Telit Cinterion brand modules, specifically the BGS5, EHS5, EHS6, EHS8, PDS5, PDS6, PDS8, ELS61, ELS81, or PLS62 product families. Check device labels, firmware banners, or management interfaces for model identification.
    Affected if Any of these Telit modem models (BGS5, EHS5/6/8, PDS5/6/8, ELS61/81, PLS62) are deployed in the environment.
  2. Confirm the firmware version
    Query the modem module for its firmware version using AT commands (such as AT+CGMR or ATI) or through the device management interface. Compare the returned version against the list of affected products which includes all versions of BGS5, EHS5, EHS6, EHS8, PDS5, PDS6, PDS8, ELS61 firmware.
    Affected if The modem firmware version matches any of the affected models (BGS5, EHS5, EHS6, EHS8, PDS5, PDS6, PDS8, ELS61) regardless of version number.
  3. Check if virtual directory feature is enabled
    Examine the modem configuration for virtual directory settings. This is typically configured through the modem's web interface, AT commands for file system configuration, or in the device's security settings. Look for configurations that map virtual paths to filesystem locations.
    Affected if Virtual directories are configured on the modem, creating the condition for the path traversal vulnerability to be exploitable.
  4. Assess local attack surface exposure
    Evaluate whether the modem's web server or file access interfaces are reachable from the local network or directly from the device. Check network exposure, authentication settings, and whether low-privileged local access to the device is possible.
    Affected if The modem is accessible locally without strong access controls, allowing a low-privileged local attacker to reach the virtual directory feature.

You are affected if you have any Telit Cinterion modem modules from the BGS5, EHS5/6/8, PDS5/6/8, or ELS61 product families with virtual directory configuration enabled and local access exposure.

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-provided firmware patches from Telit to all affected modem modules; until patches are available, minimize local attack surface by restricting device access and network exposure, and consider network segmentation to limit exposure to local attackers.

Fix this in Bgs5 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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