CVE-2023-31995
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 · uneditedHanwha IP Camera ANE-L7012R 1.41.01 is vulnerable to Cross Site Scripting (XSS).
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 Camera ANE-L7012R version 1.41.01 contains a cross-site scripting (XSS) vulnerability in its web interface. Attackers can inject malicious JavaScript code through user-supplied input, potentially allowing session hijacking or credential theft when other users view the crafted content.
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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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's web interface or check the device label/network discovery to confirm the exact model (ANE-L7012R, ANE-L6012R, ANO-L6012R, ANO-L6022R, ANO-L6082R, ANO-L7012R, ANO-L7022R, or ANO-L7082R).Affected if The model matches one of the affected models listed in the CVE.
-
Check the installed firmware versionLog into the camera's web interface and navigate to the firmware or system information page. Alternatively, use the camera's API or SNMP to query the firmware version.Affected if The firmware version is lower than 1.41.03.
-
Confirm the web interface is enabledVerify that the camera's HTTP/HTTPS web management interface is accessible and not disabled via configuration.Affected if The web interface is accessible and the firmware version is below 1.41.03.
-
Check for user-accessible input fieldsNavigate to common web interface pages that accept user input (such as device name, network settings, or custom labels) and inspect the form handling.Affected if User-supplied input fields are present in the web interface and the firmware is vulnerable.
The environment is affected if the camera model matches one of the affected models and the installed firmware version is below 1.41.03 with the web interface enabled and accessible.
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 output encoding and input validation to all user-facing fields in the camera's web interface. Update to a patched firmware version if available from the vendor.
Firmware version 1.41.03 or later
- 1. Navigate to the official Hanwha Vision support website (hanwhavisionamerica.com or www.hanwhavision.com)
- 2. Locate the support or downloads section for your specific camera model (ANE-L7012R, ANE-L6012R, or other affected models)
- 3. Download the firmware version 1.41.03 or the latest available firmware version
- 4. Access the camera's web management interface
- 5. Navigate to the firmware upgrade or system maintenance section
- 6. Upload and apply the downloaded firmware file
- 7. Verify the upgrade was successful by checking the firmware version in the camera settings
- 8. Test that the XSS vulnerability is no longer present
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-31995 — 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-31995 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