Use of Hard-coded Credentials in Viidure Dashcam Android Application
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Viidure | Dashcam Android Application | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Viidure | Dashcam Android Application |
|
Vendor Workaround
Viidure did not respond to CISA's coordination attempts. Users of affected versions of the Viidure Dashcam Android Application are advised to contact Viidure customer support for additional information https://viidure.app/. https://viidure.app/
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.416% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Viidure
Viidure dashcam Android Application |
|
| Vendors & Products |
Viidure
Viidure dashcam Android Application |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The Viidure Android application embeds permanent, plaintext cloud storage credentials within its compiled code. These credentials provide full access to critical platform storage, including the ability to read, modify, or delete operational files such as firmware and application binaries. | |
| Title | Use of Hard-coded Credentials in Viidure Dashcam Android Application | |
| Weaknesses | CWE-798 | |
| References |
| |
| Metrics |
cvssV3_1
|