CVE-2023-31994
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 · uneditedCertain Hanwha products are vulnerable to Denial of Service (DoS). ck vector is: When an empty UDP packet is sent to the listening service, the service thread results in a non-functional service (DoS) via WS Discovery and Hanwha proprietary discovery services. This affects IP Camera ANE-L7012R 1.41.01 and IP Camera XNV-9082R 2.10.02.
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 confidenceHanwha IP cameras ANE-L7012R (v1.41.01) and XNV-9082R (v2.10.02) contain a denial-of-service vulnerability in their WS Discovery and proprietary discovery services. An attacker can send an empty UDP packet to the listening service port, causing the service thread to become non-functional and rendering the device unresponsive.
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< 1.41.03< 1.41.03< 1.41.03< 1.41.03< 1.41.03< 1.41.03< 1.41.03< 1.41.03CVSS 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
- None
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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 camera modelAccess the camera web interface or check the device label to determine the exact model number (e.g., ANE-L7012R, XNV-9082R, or one of the Ano/Ane variants)Affected if The model matches any of these: Ane L6012r, Ane L7012r, Ano L6012r, Ano L6022r, Ano L6082r, Ano L7012r, Ano L7022r, or Ano L7082r
-
Check the installed firmware versionLog into the camera web interface, go to the firmware or system information page, and record the firmware version numberAffected if The firmware version is below 1.41.03 (for example, 1.41.01 or 2.10.02)
-
Verify WS-Discovery service is enabledCheck the camera network settings or services configuration for WS-Discovery or ONVIF discovery service statusAffected if WS-Discovery or ONVIF discovery is enabled and running on the device
-
Check discovery service port exposureUse a network port scanner or check firewall rules to verify if UDP port 3702 (WS-Discovery) or the proprietary discovery port is accessible from untrusted network segmentsAffected if UDP port 3702 or discovery service ports are open to untrusted/internal networks without firewall filtering
The device is affected if it is one of the listed models, runs firmware below version 1.41.03, has WS-Discovery enabled, and has the discovery ports accessible to network attackers.
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 · scoped1.41.03
Apply vendor firmware updates when available. As an interim measure, restrict network access to discovery service ports (UDP 3702 for WS-Discovery typically) via firewall rules or network segmentation to prevent unauthorized external attackers from reaching the discovery service.
Firmware version 1.41.03 or later for affected ANE-L and ANO-L series cameras
- Identify the specific camera model from the affected list (ANE-L7012R, XNV-9082R, or any ANE/ANO L-series model)
- Access the camera's web interface or management console
- Navigate to the firmware upgrade section (usually under Maintenance, Settings, or System)
- Download the firmware version 1.41.03 or later from the official Hanwha Vision support website (hanwhavisionamerica.com or www.hanwhavision.com)
- Upload the firmware file to the camera device
- Wait for the firmware upgrade process to complete (do not power off the device during upgrade)
- Reboot the camera device if not done automatically
- Verify the firmware version has been updated to 1.41.03 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-31994 — 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-31994 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