GV-Eye Relay Payment API Key Vulnerability
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| GeoVision Inc. | GV-Eye | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Geovision | Gv-eye |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.152% probability within 30 days)
| Link | Providers |
|---|---|
| https://www.geovision.com.tw/cyber_security.php |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Geovision
Geovision gv-eye |
|
| Vendors & Products |
Geovision
Geovision gv-eye |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | An API key is hardcoded and retrievable from the application package. Since Android applications can be reverse engineered, embedding sensitive API credentials directly in the client application may allow unauthorized users to extract and misuse the key. | |
| Title | GV-Eye Relay Payment API Key Vulnerability | |
| First Time appeared |
Geovision Inc.
Geovision Inc. gv-eye |
|
| Weaknesses | CWE-312 CWE-540 CWE-798 |
|
| CPEs | cpe:2.3:a:geovision_inc.:gv-eye:v3.6.0:*:android:*:*:*:*:* cpe:2.3:a:geovision_inc.:gv-eye:v3.7.2:*:android:*:*:*:*:* |
|
| Vendors & Products |
Geovision Inc.
Geovision Inc. gv-eye |
|
| References |
| |
| Metrics |
cvssV3_1
|