CVE-2019-18228
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 IP cameras Multiple equIP Series Cameras, A vulnerability exists in the affected products where a specially crafted HTTP packet request could result in a denial of service.
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 · low confidenceA denial of service vulnerability exists in Honeywell equIP series IP cameras where specially crafted HTTP packet requests can cause the device's web service to fail or become unresponsive, potentially disrupting video surveillance operations.
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
- 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 the camera modelCheck the device label, packaging, or access the web interface to view the model name under System > Device Info or similar. Look for model numbers: H2w2pc1m, H2w2per3, H4w2per2, H4w2per3, H2w4per3, H4w4per2, H4w4per3, or H4w8pr2.Affected if The model matches any of the eight affected models listed in the CVE.
-
Check the firmware versionAccess the camera web interface and navigate to System > Firmware/Software or System > Device Info. Alternatively, use the ONVIF protocol or manufacturer discovery tool to query the firmware version.Affected if All firmware versions of the affected models are vulnerable since the CVE lists all versions.
-
Verify web service statusAttempt to access the camera HTTP interface via browser at http://[camera-ip]. Observe whether the login page loads or if the service is unresponsive, slow, or returning errors.Affected if The web service is unresponsive, returns errors, or has recently experienced unexplained outages.
-
Check HTTP network exposureReview firewall rules, network segmentation, and access control lists to determine if the camera HTTP port (typically 80) is accessible from untrusted networks or the internet.Affected if Port 80/HTTP is exposed to untrusted networks, increasing the likelihood of exploitation.
-
Review device logs for anomaliesAccess camera logs via the web interface under Logs or Diagnostics. Look for timestamps, HTTP request patterns, or service restarts that correlate with DoS conditions.Affected if Logs show repeated service failures, unusual HTTP request patterns, or unexpected restarts.
You are affected if your Honeywell IP camera is any of the eight listed models (H2w2pc1m, H2w2per3, H4w2per2, H4w2per3, H2w4per3, H4w4per2, H4w4per3, or H4w8pr2) and the web service is network-accessible, since all firmware versions of these models are vulnerable.
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 dataContact Honeywell for firmware updates addressing this vulnerability; in the interim, restrict HTTP access to these devices using network segmentation or firewall rules to limit exposure to untrusted networks.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-18228 — 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-18228 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