CVE-2019-19885
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 · uneditedIn Bender COMTRAXX, user authorization is validated for most, but not all, routes in the system. A user with knowledge about the routes can read and write configuration data without prior authorization. This affects COM465IP, COM465DP, COM465ID, CP700, CP907, and CP915 devices before 4.2.0.
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 confidenceIn Bender COMTRAXX, authorization checks are inconsistently applied across web routes. Some routes allow unauthenticated access, enabling an attacker with knowledge of specific URLs to read and write device configuration data without credentials. This affects multiple COM465 and CP device models.
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< 4.2.0< 4.2.0< 4.2.0< 4.2.0< 4.2.0< 4.2.0CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 Bender device modelAccess the device web interface, check the product label, or query via SNMP to determine if the device is one of: Com465ip, Com465dp, Com465id, Cp700, Cp907, or Cp915Affected if The device model matches one of the affected models listed in the CVE
-
Determine the installed firmware versionLog into the device web interface and navigate to the system information or firmware version page. Alternatively, check via the device management interface or CLI if availableAffected if The firmware version is less than 4.2.0 (for example, 4.1.x or earlier)
-
Verify web interface accessibilityAttempt to reach the device web management interface over HTTP/HTTPS from a network location. Determine if the interface is exposed to network segments beyond the trusted management networkAffected if The web interface is accessible from network segments that should not have management access
-
Test for unauthenticated route accessUsing a web browser or HTTP tool, attempt to access known configuration-related URLs on the device without providing any login credentials. Common paths may include those related to device settings, configuration export/import, or system parametersAffected if Any configuration-related pages or APIs are accessible without authentication prompts or login requirements
-
Review network exposure of management interfaceCheck firewall rules, VLAN configurations, or access control lists to determine if the device management interface is reachable from untrusted network segments or the internetAffected if The device web management interface can be reached from untrusted network segments without additional authentication barriers
A device is likely affected if it is a Com465ip, Com465dp, Com465id, Cp700, Cp907, or Cp915 model running firmware version earlier than 4.2.0 and its web interface is network-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 · scoped4.2.0
Upgrade affected devices to firmware version 4.2.0 or later. Until patched, restrict network access to management interfaces via firewall or VLAN isolation to reduce attack surface.
Firmware 4.2.0
- Obtain the firmware version 4.2.0 or later from the vendor (Bender) via their official support channels or website
- Review the device-specific firmware upgrade instructions provided by Bender
- Ensure the upgrade process is performed in a controlled environment with proper backup of existing configuration
- Upload the firmware to the affected device (COM465IP, COM465DP, COM465ID, CP700, CP907, or CP915) following vendor procedures
- Verify the firmware upgrade was successful and the device is functioning properly
- Confirm the fix by verifying that authorization is now required for all routes in the system
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19885 — 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-19885 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