CVE-2023-5038
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 · uneditedbadmonkey, a Security Researcher has found a flaw that allows for a unauthenticated DoS attack on the camera. An attacker runs a crafted URL, nobody can access the web management page of the camera. and must manually restart the device or re-power it. The manufacturer has released patch firmware for the flaw, please refer to the manufacturer's report for details and workarounds.
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 confidenceAn unauthenticated attacker can send a crafted URL to the camera's web management interface, causing the web service to crash. This renders the management page inaccessible and requires physical intervention (manual restart or power cycle) to recover the device.
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.16< 1.41.16< 1.41.16< 1.41.16< 1.41.16< 1.41.16< 1.41.16< 1.41.16CVSS 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
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 your camera modelAccess the camera's web management interface or check the physical device label to determine the exact model number (e.g., Ano L6012r, Anv L6022r, etc.)Affected if The model matches one of: Ano L6012r, Ano L6022r, Anv L6012r, Ano L6082r, Ane L6012r, Anv L6082r, Ano L7082r, or Ane L7012r
-
Check the installed firmware versionLog into the camera's web interface and navigate to the system or information page to view the current firmware version. Alternatively, use the manufacturer's discovery tool or check via ONVIF if available.Affected if The firmware version is lower than 1.41.16 (e.g., 1.41.15, 1.40.x, etc.)
-
Confirm the device has not been patchedIf you previously updated the firmware, verify the exact version number in the system information page to confirm it is 1.41.16 or higherAffected if The firmware version cannot be confirmed as 1.41.16 or higher
You are affected if your camera model is one of the eight listed models AND the installed firmware version is below 1.41.16, as this combination allows an unauthenticated attacker to crash the web service via a crafted URL.
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.16
Apply the vendor-released patch firmware to affected cameras. If patching is not immediately possible, restrict access to the camera's web management interface to trusted networks or IP addresses.
Firmware version 1.41.16 or later for Ano L6012r, Ano L6022r, Anv L6012r, Ano L6082r, Ane L6012r, Anv L6082r, Ano L7082r, Ane L7012r
- Identify the exact model number of the affected Hanwha Vision camera (L6012r, L6022r, L6082r, L7012r, or L7082r variant)
- Access the camera's web management interface using an administrator account
- Navigate to the firmware upgrade section (usually found under Settings > System > Firmware Upgrade or Maintenance > Upgrade)
- Download the firmware version 1.41.16 or later from the official Hanwha Vision support website (www.hanwhavision.com)
- Upload the firmware file through the web interface or use the manufacturer's firmware update tool
- Wait for the upgrade process to complete - do not power off the device during the update
- After the firmware update completes, verify the new version in the system information page
- Restart the camera through the web interface to ensure all services load with the new firmware
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-5038 — 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-5038 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