CVE-2023-5747
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 · uneditedBashis, a Security Researcher at IPVM has found a flaw that allows for a remote code execution during the installation of Wave on the camera device. The Wave server application in camera device was vulnerable to command injection allowing an attacker to run arbitrary code. HanwhaVision has released patched firmware for the highlighted flaw. Please refer to the hanwhavision security report for more information and solution."
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 · moderate confidenceA command injection vulnerability in the Wave server application on HanwhaVision camera devices allows remote attackers to execute arbitrary code during the installation process. The vulnerability stems from improper input validation in the Wave component, enabling malicious command injection that can lead to complete device compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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< 5.1.1.37647= 2.21.02= 2.21.02CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the Wave Server Software versionAccess the HanwhaVision device management interface or check the installed Wave Server Software version through the system information or about section. Compare the version number to the affected range: versions prior to 5.1.1.37647 are vulnerable.Affected if Wave Server Software version is less than 5.1.1.37647
-
Identify the camera firmware version for Pno A6081r E1tAccess the camera web interface or use the device's firmware check feature. Navigate to the firmware or system information page to view the installed firmware version.Affected if Firmware version on Pno A6081r E1t equals exactly 2.21.02
-
Identify the camera firmware version for Pno A6081r E2tAccess the camera web interface or use the device's firmware check feature. Navigate to the firmware or system information page to view the installed firmware version.Affected if Firmware version on Pno A6081r E2t equals exactly 2.21.02
-
Verify if the Wave server component is installedCheck the device or management system for the presence of the Wave server application component. This is typically found in the software feature list or installed applications on the device.Affected if The Wave server application is installed and the version cannot be verified as 5.1.1.37647 or higher
A device is affected if it runs Wave Server Software versions below 5.1.1.37647, or if it is a Pno A6081r E1t or E2t camera with firmware version 2.21.02, and the Wave server component is present.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.1.1.37647
Apply the patched firmware released by HanwhaVision to all affected camera devices. For devices that cannot be immediately updated, network segmentation and restricting access to the camera management interfaces can reduce exposure until patching is feasible.
Wave Server Software >= 5.1.1.37647; Camera firmware > 2.21.02 (obtain exact version from HanwhaVision)
- Upgrade Wave Server Software to version 5.1.1.37647 or later
- For Pno A6081r E1t camera: Apply the patched firmware released by HanwhaVision (version higher than 2.21.02)
- For Pno A6081r E2t camera: Apply the patched firmware released by HanwhaVision (version higher than 2.21.02)
- After upgrading, verify the Wave server application is functioning correctly and the vulnerability is resolved
- Refer to the official HanwhaVision security report for detailed firmware download and installation instructions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-5747 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-5747 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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