CVE-2019-18226
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 · uneditedHoneywell equIP series and Performance series IP cameras and recorders, A vulnerability exists in the affected products where IP cameras and recorders have a potential replay attack vulnerability as a weak authentication method is retained for compatibility with legacy products.
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 replay attack vulnerability in Honeywell equIP and Performance series IP cameras and recorders allows attackers to capture and replay valid authentication credentials due to a weak authentication method retained for legacy product compatibility.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 device modelAccess the camera's web interface or check the device label to confirm the exact model number (e.g., H2w2pc1m, H4w4per3). Verify against the list of affected models.Affected if The device model matches any of: H2w2pc1m, H2w2per3, H4w2per2, H4w2per3, H4w4per2, H4w4per3, H4w8pr2, or H2w4per3.
-
Determine the firmware versionLog into the camera's web interface and navigate to the System or About section to view the installed firmware version.Affected if The camera is one of the affected models and is running any firmware version (all versions are affected).
-
Check for legacy authentication settingsLocate the authentication or security settings in the camera's web interface or administration panel. Look for options related to legacy authentication, backward compatibility, or older authentication protocols.Affected if Legacy or backward-compatible authentication methods are enabled on the device.
-
Review authentication logs for replay patternsExamine the camera's authentication or access logs for repeated identical login attempts from different sessions, unusual timing patterns, or duplicate credential usage.Affected if Logs show authentication attempts with identical credentials appearing repeatedly or at suspicious intervals.
-
Inspect network traffic for credential replayUse a network sniffer to capture authentication packets and verify whether the same credentials are being transmitted verbatim across multiple sessions without modification.Affected if The same authentication data is observed being transmitted repeatedly without session-specific variation.
A user is affected if they have any of the listed Honeywell camera models with legacy authentication enabled, as all firmware versions are vulnerable to credential replay attacks.
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.
From vendor dataUpdate to vendor-provided firmware that addresses the weak authentication; if unavailable, implement network segmentation and monitor for anomalous authentication patterns. Consider disabling legacy authentication protocols if supported.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-18226 — 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-2019-18226 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