dbcve.org
Dss ExpressApplication · Dahuasecurity

CVE-2022-45429

HIGH · 7.5 CVSS v3.1 Published 2022-12-27
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Some Dahua software products have a vulnerability of server-side request forgery (SSRF). An Attacker can access internal resources by concatenating links (URL) that conform to specific rules.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-918

The server can be induced to make requests to a URL an attacker controls, turning it into a proxy into internal networks and cloud metadata services. It's especially dangerous behind a trusted network boundary. The fix is strict allow-listing of destinations and blocking access to internal address ranges.

General guidance for the server-side request forgery (ssrf) class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Dss ExpressApplication
Affected:= 7.002.1760000.2= 8.0.2= 8.0.4= 8.1= 8.1.1
Dss ProfessionalApplication
Affected:= 7.002.1760000.2= 8.0.2= 8.0.4= 8.1= 8.1.1
Dhi Dss7016d S2 FirmwareOperating system
Affected:= 1.001.0000001.2= 8.0.2= 8.0.4= 8.1
Dhi Dss7016dr S2 FirmwareOperating system
Affected:= 1.001.0000001.2= 8.0.2= 8.0.4= 8.1
Dhi Dss4004 S2 FirmwareOperating system
Affected:= 1.001.0000001.2= 8.0.2= 8.0.4= 8.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch www.dahuasecurity.com →
Recommended fix Moderate confidence

Obtain the fixed release version from vendor advisory at https://www.dahuasecurity.com/support/cybersecurity/details/1137 - versions beyond 8.1 contain the fix

  1. 1. Identify the specific Dahua product model (Dss Express, Dss Professional, or specific firmware device) from the affected list
  2. 2. Access the vendor security advisory at https://www.dahuasecurity.com/support/cybersecurity/details/1137 to obtain the official fixed version for your product
  3. 3. Download the latest patched firmware/software version from Dahua's official support portal
  4. 4. Back up current system configuration before applying the update
  5. 5. Apply the firmware update or software patch according to Dahua's installation documentation
  6. 6. Verify the SSRF vulnerability is resolved by confirming the affected URL parameter no longer allows arbitrary internal resource access
  7. 7. After patching, restrict network exposure of the management interface to minimize SSRF attack surface
Caveat Review Dahua release notes for any configuration or compatibility changes between your current version and the fixed version

Generated from the published advisory — verify against the referenced sources before acting.

We can apply and verify the patch for your build — typical engagement from $3,200. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-45429 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-45429 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data