cve.bz

CVE-2022-45424 dahuasecurity

5.3 mediumEPSS 0.7%Fix available

Medium (5.3) in dahuasecurity. EPSS 0.7% estimated probability of exploitation activity in the next 30 days.

On this page
Some Dahua software products have a vulnerability of unauthenticated request of AES crypto key. An attacker can obtain the AES crypto key by sending a specific crafted packet to the vulnerable interface.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 55th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2025-04-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-306 Missing Authentication for Critical Functionality
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2022-45424 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-45424?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-45424?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-45424 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
dahuasecurity:dss_express7.002.1760000.2
dahuasecurity:dss_express8.0.2
dahuasecurity:dss_express8.0.4
dahuasecurity:dss_express8.1
dahuasecurity:dss_express8.1.1
dahuasecurity:dss_professional7.002.1760000.2
dahuasecurity:dss_professional8.0.2
dahuasecurity:dss_professional8.0.4
dahuasecurity:dss_professional8.1
dahuasecurity:dss_professional8.1.1
dahuasecurity:dhi-dss7016d-s2_firmware1.001.0000001.2
dahuasecurity:dhi-dss7016d-s2_firmware8.0.2
dahuasecurity:dhi-dss7016d-s2_firmware8.0.4
dahuasecurity:dhi-dss7016d-s2_firmware8.1
dahuasecurity:dhi-dss7016dr-s2_firmware1.001.0000001.2
dahuasecurity:dhi-dss7016dr-s2_firmware8.0.2
dahuasecurity:dhi-dss7016dr-s2_firmware8.0.4
dahuasecurity:dhi-dss7016dr-s2_firmware8.1
dahuasecurity:dhi-dss4004-s2_firmware1.001.0000001.2
dahuasecurity:dhi-dss4004-s2_firmware8.0.2
dahuasecurity:dhi-dss4004-s2_firmware8.0.4
dahuasecurity:dhi-dss4004-s2_firmware8.1

Attack patterns (CAPEC)

  • CAPEC-12 Choosing Message Identifier Likelihood: High · Severity: High
  • CAPEC-36 Using Unpublished Interfaces or Functionality Likelihood: Medium · Severity: High
  • CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
  • CAPEC-166 Force the System to Reset Values Severity: Medium
  • CAPEC-216 Communication Channel Manipulation

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON