dbcve.org
Hbd3pr2 FirmwareOperating system · Honeywell

CVE-2019-13523

MEDIUM · 5.3 CVSS v3.1 Published 2019-09-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
In Honeywell Performance IP Cameras and Performance NVRs, the integrated web server of the affected devices could allow remote attackers to obtain web configuration data in JSON format for IP cameras and NVRs (Network Video Recorders), which can be accessed without authentication over the network. Affected performance IP Cameras: HBD3PR2,H4D3PRV3,HED3PR3,H4D3PRV2,HBD3PR1,H4W8PR2,HBW8PR2,H2W2PC1M,H2W4PER3,H2W2PER3,HEW2PER3,HEW4PER3B,HBW2PER1,HEW4PER2,HEW4PER2B,HEW2PER2,H4W2PER2,HBW2PER2,H4W2PER3, and HPW2P1. Affected Performance Series NVRs: HEN08104,HEN08144,HEN081124,HEN16104,HEN16144,HEN16184,HEN16204,HEN162244,HEN16284,HEN16304,HEN16384,HEN32104,HEN321124,HEN32204,HEN32284,HEN322164,HEN32304, HEN32384,HEN323164,HEN64204,HEN64304,HEN643164,HEN643324,HEN643484,HEN04103,HEN04113,HEN04123,HEN08103,HEN08113,HEN08123,HEN08143,HEN16103,HEN16123,HEN16143,HEN16163,HEN04103L,HEN08103L,HEN16103L,HEN32103L.

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 · high confidence

Honeywell Performance IP Cameras and NVRs contain an unauthenticated information disclosure vulnerability in their integrated web servers. Remote attackers can obtain sensitive web configuration data in JSON format for affected IP cameras and NVRs by accessing specific endpoints without any authentication. This exposes device configuration details over the network to unauthenticated users.

MitigationApply available vendor firmware updates or patches for affected devices. If no patch is available, implement network segmentation to isolate camera/NVR systems from untrusted networks and restrict web server access through firewall rules to authorized IP addresses only.

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
Hbd3pr2 FirmwareOperating system
Affected:all versions
H4d3prv3 FirmwareOperating system
Affected:all versions
Hed3pr3 FirmwareOperating system
Affected:all versions
H4d3prv2 FirmwareOperating system
Affected:all versions
Hbd3pr1 FirmwareOperating system
Affected:all versions
H4w8pr2 FirmwareOperating system
Affected:all versions
Hbw8pr2 FirmwareOperating system
Affected:all versions
H2w2pc1m FirmwareOperating system
Affected:all versions

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model and firmware version
    Access the device web interface or use SNMP/SSH to query the device for its model number (Hbd3pr2, H4d3prv3, Hed3pr3, H4d3prv2, Hbd3pr1, H4w8pr2, Hbw8pr2, or H2w2pc1m) and firmware version information. Check device labels, web login page source, or system information pages.
    Affected if The device model matches one of the affected models (Hbd3pr2, H4d3prv3, Hed3prv3, H4d3prv2, Hbd3pr1, H4w8pr2, Hbw8pr2, H2w2pc1m) regardless of firmware version, as all versions are affected.
  2. Confirm web server is enabled and network accessible
    Attempt to reach the device IP address on HTTP (port 80) or HTTPS (port 443) from a network location. Use a browser or curl command to verify the web server responds.
    Affected if The web server responds and is accessible from the network, indicating the attack surface is present.
  3. Test for unauthenticated access to configuration endpoints
    Using curl or a browser without providing any credentials, attempt to access common configuration endpoints such as /config, /settings, /api/config, /cgi-bin/config, or similar paths that return JSON configuration data. Observe if the device returns configuration information without requiring login.
    Affected if The device returns JSON configuration data or sensitive web configuration details without requiring any authentication credentials.
  4. Verify sensitive data exposure in responses
    Examine any JSON responses obtained from unauthenticated endpoints. Look for sensitive configuration details such as network settings, user accounts, authentication credentials, IP addresses, or system parameters that should not be publicly accessible.
    Affected if Sensitive configuration data including device settings, network parameters, or authentication-related information is exposed in the response to unauthenticated requests.

A user is affected if they have a Honeywell IP camera or NVR from the affected model list (Hbd3pr2, H4d3prv3, Hed3pr3, H4d3prv2, Hbd3pr1, H4w8pr2, Hbw8pr2, H2w2pc1m) with an accessible web server that returns sensitive configuration data in JSON format without requiring authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply available vendor firmware updates or patches for affected devices. If no patch is available, implement network segmentation to isolate camera/NVR systems from untrusted networks and restrict web server access through firewall rules to authorized IP addresses only.

Fix this in Hbd3pr2 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-13523 — 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-2019-13523 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