Skip to main content

Viidure Dashcam EUVDEUVD-2026-89457

| CVE-2026-94204 HIGH
Incorrect Permission Assignment for Critical Resource (CWE-732)
2026-09-29 icscert GHSA-947q-qf7p-x7c7
8.7
CVSS 4.0 · Vendor: icscert
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V13 - Configuration Permission assignment review
Impact

This is a genuine, high-real-risk data exposure rather than an inflated CVSS score. The vendor CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N, VC:H) is internally consistent with the description: a cloud storage bucket set to public-read is reachable by anyone on the internet with no authentication, no user interaction, and trivial complexity - the classic profile of a discoverable, scriptable exposure. The 8.7 score is driven entirely by confidentiality (VC:H) with VI:N/VA:N, which correctly reflects a read-only disclosure with no integrity or availability impact. No EPSS score, no CISA KEV listing, and no public exploit code were provided, so exploitation status is 'no public exploit identified at time of analysis' - but note that for misconfigured public buckets, 'exploitation' requires only knowing/guessing the bucket URL, so the absence of a formal PoC understates practical accessibility. Conflicting/soft signals to verify: this is reported as an ICS advisory (icscert, ICSA-26-272-07) for a consumer dashcam Android app, and the flaw is a server-side/cloud misconfiguration, not a defect in the shipped Android binary named by the CPE - remediation is a vendor-side ACL change, so there may be no downloadable patch. Overall: real priority for affected users' privacy despite lacking KEV/EPSS/PoC signals.

This Week Schedule remediation this week. Why: Active threat signals + CRITICAL/HIGH severity.
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 29, 2026

Unrestricted public read access to the Viidure dashcam platform's central cloud storage bucket exposes sensitive user records, live dashcam footage, application packages, and firmware files to anyone on the internet. Because CPE data ties the affected asset to the Viidure Dashcam Android application and the bucket is the shared storage backend for the whole platform, the exposure is platform-wide rather than isolated to a single customer or object. The issue is remotely reachable by unauthenticated attackers (CVSS 4.0 vector AV:N/PR:N/UI:N) with high confidentiality impact only (VC:H, VI:N, VA:N) and a CVSS score of 8.7; no public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, although accessing the data requires nothing more than an unauthenticated request to the bucket. Our independent assessment agrees this is a genuine, high-real-risk data exposure rather than an inflated CVSS score.

RemediationAI

No vendor-released patch was identified at time of analysis, and for a CWE-732 public-read bucket misconfiguration the fix is configuration-side rather than a code update. Immediately set the bucket to private, remove any public-read ACL or bucket policy granting the anonymous or AllUsers principal GetObject/ListBucket, and enable account- or organization-level Block Public Access so the setting cannot be silently reverted; verify with an unauthenticated request from outside the tenancy. Review object access logs (e.g., S3 server access logs or CloudTrail data events) for prior enumeration and bulk downloads, and treat everything in the bucket as compromised: rotate any credentials, API keys, or signing material shipped inside exposed application packages or firmware, invalidate previously public object URLs, and notify affected users whose records or footage were exposed. If application or firmware delivery depends on public object URLs, migrate to signed, short-lived URLs or a CDN with an origin access identity - the trade-off is added signing infrastructure and possible breakage of cached or hard-coded links in already-deployed clients, which must be updated or redirected. Confirm current guidance against the ICS CERT advisory ICSA-26-272-07 (https://www.cisa.gov/news-events/ics-advisories/icsa-26-272-07), the CSAF JSON (https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-272-07.json), and the vendor site https://viidure.app/ for any published fix, remediation timeline, or vendor statement.

Affected VersionsENISA

Dashcam Android Application 0 ≤3.3.1.260403

Affected Packages

euvd dashcam_android_application no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-732 (Incorrect Permission Assignment for Critical Resource): the object storage bucket backing the dashcam platform is configured with public-read permissions, either through a legacy ACL or a bucket policy that grants the anonymous principal object read (and likely list) operations. This is a cloud object-storage access-control failure rather than a memory-safety or injection flaw - there is no exploit primitive to build, only an over-permissive policy that any internet host can exercise over HTTPS. The CPE cpe:2.3:a:viidure:dashcam_android_application:*:*:*:*:*:*:*:* indicates the Viidure Dashcam Android application is the affected product, with the wildcard version confirming no fixed release is identified; the bucket functions as shared infrastructure for the mobile app, storing user records, live footage, installable app packages, and device firmware. The CVSS 4.0 profile is consistent with a read-only misconfiguration: network-vectored, no privileges or user interaction required, high confidentiality loss, but no integrity (VI:N) and no availability (VA:N) impact, which maps cleanly to anonymous read access without write or delete capability. Reported by ICS CERT under advisory ICSA-26-272-07, which places this in the ICS/mobile-product advisory stream and signals that the vendor's platform, not just a single deployment, is in scope.

Know when Dashcam Android Application gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (icscert) PRIMARY 8.7 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (icscert) · only source for this CVE.

CVSS VectorVendor: icscert

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

The central cloud storage backend for the entire dashcam platform is misconfigured with public-read permissions, allowing unrestricted access to all stored objects. Because this bucket serves as shared storage for the platform, sensitive user records, live dashcam footage, application packages, and firmware files are exposed to anyone on the internet.

Executive ViewAI

Why It Matters

The Viidure dashcam platform's central cloud storage bucket is publicly accessible, exposing sensitive user records, live dashcam footage, and firmware to unauthenticated attackers. This platform-wide exposure affects all customers and could result in privacy violations, regulatory penalties, and reputational harm. Leadership should prioritize immediate mitigation; no vendor-released patch identified at time of analysis.

Business Impact: Severe
Compensating Controls

Immediately set the storage bucket to private, enforce authentication for all access, enable access logging and monitoring, and rotate any exposed credentials or tokens. Additionally, implement network-level restrictions and encrypt data at rest with keys not publicly accessible.

Threat Intelligence Overview

EPSS Score
0.3%
Top 83% exploitable
Threat Intel
1
1 sources
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat Yes
Deciding rule
Active threat signals + CRITICAL/HIGH severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
Very High
Technical Impact
Partial

Priority Score

54
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: +10
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Threat IntelligenceMISP

CISA Advisories
Sources: CISA Vulnrichment, CISA (public domain)

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy