CVE-2024-4063 json
EZVIZ CS-C6-21WFR-8 Davinci Application certificate validation
published 2y ago modified 4mo ago also EUVD-2024-32628
- cvss
- 3.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 27%
- public exploits
- 0
- none known
Summary
A vulnerability was found in EZVIZ CS-C6-21WFR-8 5.2.7 Build 170628. It has been classified as problematic. This affects an unknown part of the component Davinci Application. The manipulation leads to improper certificate validation. It is possible to initiate the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The identifier VDB-261789 was assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.
Is CVE-2024-4063 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2y ago
Exploit prediction
0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 3.7 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N |
| CNA | 3.0 | 3.7 | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N |
| CNA | 2.0 | 2.6 | AV:N/AC:H/Au:N/C:P/I:N/A:N |
Affected products
- EZVIZ CS-C6-21WFR-8
Classification
- Weakness
-
- CWE-295 Improper Certificate Validation
References
-
vuldb.com
/?id.261789
vdb-entry
-
vuldb.com
/?ctiid.261789
signature, permissions-required
-
vuldb.com
/?submit.316408
third-party-advisory
-
github.com
/kzLiu2017/CVE_Document/blob/main/CVE_%20advisory_ezviz.pdf
related
Sources
- CVE List CVE-2024-4063
- NVD CVE-2024-4063
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.