| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.7 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Dahua IPC-HX3XXX, HX5XXX, HUM7XXX, VTO75X95X, VTO65XXX, VTH542XH, SD1A1, SD22, SD49, SD50, SD52C, SD6AL, TPC-BF1241, TPC-BF2221, TPC-SD2221, TPC-BF5XXX, TPC-SD8X21 and TPC-PT8X21B. The affected element is an unknown function of the component Data Packet Handler. This manipulation causes improper authentication. This vulnerability is registered as CVE-2021-33044. Remote exploitation of the attack is possible. Furthermore, an exploit is available. You should upgrade the affected component.
Details
A vulnerability classified as critical was found in Dahua IPC-HX3XXX, HX5XXX, HUM7XXX, VTO75X95X, VTO65XXX, VTH542XH, SD1A1, SD22, SD49, SD50, SD52C, SD6AL, TPC-BF1241, TPC-BF2221, TPC-SD2221, TPC-BF5XXX, TPC-SD8X21 and TPC-PT8X21B. Affected by this vulnerability is some unknown functionality of the component Data Packet Handler. The manipulation with an unknown input leads to a improper authentication vulnerability. The CWE definition for the vulnerability is CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
The identity authentication bypass vulnerability found in some Dahua products during the login process. Attackers can bypass device identity authentication by constructing malicious data packets.
The weakness was published 09/11/2021. The advisory is shared at dahuasecurity.com. This vulnerability is known as CVE-2021-33044. Technical details are unknown but an exploit is available.
It is declared as attacked. The CISA Known Exploited Vulnerabilities Catalog lists this issue since 08/21/2024 with a due date of 09/11/2024:
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.Upgrading eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
- HUM7XXX
- HX5XXX
- IPC-HX3XXX
- SD1A1
- SD6AL
- SD22
- SD49
- SD50
- SD52C
- TPC-BF5XXX
- TPC-BF1241
- TPC-BF2221
- TPC-PT8X21B
- TPC-SD8X21
- TPC-SD2221
- VTH542XH
- VTO65XXX
- VTO75X95X
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.9VulDB Meta Temp Score: 8.7
VulDB Base Score: 8.1
VulDB Temp Score: 7.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Improper authenticationCWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Attacked
EPSS Score: 🔍
EPSS Percentile: 🔍
KEV Added: 🔍
KEV Due: 🔍
KEV Remediation: 🔍
KEV Ransomware: 🔍
KEV Notice: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
05/17/2021 🔍09/11/2021 🔍
09/11/2021 🔍
09/30/2024 🔍
Sources
Advisory: dahuasecurity.comStatus: Confirmed
CVE: CVE-2021-33044 (🔍)
GCVE (CVE): GCVE-0-2021-33044
GCVE (VulDB): GCVE-100-182485
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 09/11/2021 11:40Updated: 09/30/2024 05:12
Changes: 09/11/2021 11:40 (36), 09/16/2021 09:32 (1), 08/21/2024 21:31 (26), 08/22/2024 03:24 (20), 09/30/2024 05:12 (1)
Complete: 🔍
Cache ID: 216:2C1:103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.