CVE-2021-38392
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 · uneditedA skilled attacker with physical access to the affected device can gain access to the hard disk drive of the device to change the telemetry region and could use this setting to interrogate or program an implantable device in any region in the world.
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 confidenceThis vulnerability exists in a medical device programmer that interfaces with implantable devices. An attacker with physical access can access the hard disk drive and modify the telemetry region setting, allowing them to interrogate or program implantable devices in any global region, bypassing regional restrictions.
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 dataall versionsCVSS 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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/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 checksWork through these to decide whether this CVE applies to you.
-
Identify device model and firmware versionLocate the device label or system information on the Boston Scientific Zoom Latitude Programmer/recorder/monitor 3120 to confirm the exact model number and current firmware versionAffected if If the device is a Zoom Latitude 3120 model with any firmware version, it falls within the affected product range
-
Locate telemetry region configurationAccess the device settings menu or configuration files to find the telemetry region setting option, typically found under device settings, regional settings, or telemetry configurationAffected if If the telemetry region setting is present and accessible through the standard user interface or configuration menus
-
Verify telemetry region modification controlsAttempt to change the telemetry region setting and observe whether authentication, password, or authorization is required before the change can be appliedAffected if If the telemetry region can be changed without requiring authenticated access, password verification, or authorization check
-
Assess physical security of storageExamine the device casing and access mechanisms to determine if the hard disk drive is physically accessible without specialized tools or if tamper-evident seals are presentAffected if If the hard disk drive compartment is accessible without breaking seals or using tools, allowing physical access to modify telemetry region settings
The environment is affected if you have a Boston Scientific Zoom Latitude 3120 programmer and the telemetry region setting can be modified without authentication or the hard disk is physically accessible without tamper detection.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement full disk encryption on the device storage, require authenticated access for telemetry region changes, add tamper detection mechanisms, and implement secure boot to prevent unauthorized modifications to the firmware or configuration.
- Consultation8.0 h
- Implementation40.0 h
- Testing24.0 h
- Review / QA16.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $24,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-38392 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-38392 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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