CVE-2017-10719: n/a vulnerability

CVE-2017-10719: Recently it was discovered as a part of the research on IoT devices in the most recent firmware for Shekar...

Recently it was discovered as a part of the research on IoT devices in the most recent firmware for Shekar Endoscope that the device has default Wi-Fi credentials that are exactly the same for every device. This device acts as an Endoscope camera that allows its users to use it in various industrial systems and settings, car garages, and also in some cases in the medical clinics to get access to areas that are difficult for a human being to reach. Any breach of this system can allow an attacker to get access to video feed and pictures viewed by that user and might allow them to get a foot hold in air gapped networks especially in case of nation critical infrastructure/industries.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 5, 2024, 17:41 UTC (UTC+00:00)

Security readout for executives and security teams

This CVE describes Shekar Endoscope devices shipping with the same default Wi-Fi credentials across devices. If deployed unchanged, someone who can reach the device wireless network may view camera images or video. The sources warn this could matter in industrial, garage, medical, or isolated network environments. Exposure is most likely where Shekar Endoscope or boriscope camera devices are still deployed with factory Wi-Fi settings, especially near sensitive industrial, clinical, or segmented networks. Treat this as a targeted IoT hygiene issue. Prioritize environments where camera privacy, industrial operations, medical settings, or isolated networks are involved. Mitigation focus: Inventory Shekar Endoscope or boriscope devices in operational and clinical environments.; Change default Wi-Fi credentials wherever the device supports it.; Isolate device Wi-Fi from corporate, clinical, and operational networks..

Prepared: Jun 6, 2026, 20:39 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2017-10719 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Jun 17, 2019, 21:24 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
20190609 Newly releases IoT security issuesCVE reference · mailing-list, x_refsource_BUGTRAQ
https://github.com/ethanhunnt/IoT_vulnerabilities/blob/master/Shekar_boriscope_sec_issues.pdfCVE reference · x_refsource_MISC

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.