CVE-2019-6531
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 · uneditedAn attacker could retrieve passwords from a HTTP GET request from the Kunbus PR100088 Modbus gateway versions prior to Release R02 (or Software Version 1.1.13166) if the attacker is in an MITM position.
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 confidenceThe Kunbus PR100088 Modbus gateway transmits passwords in cleartext via HTTP GET requests, allowing an attacker in a Man-in-the-Middle (MITM) position to intercept and retrieve credentials. This is a sensitive data exposure vulnerability due to lack of encryption on authentication transmissions.
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.1.13166CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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.
-
Check the installed firmware versionAccess the device's web interface or administrative console and locate the firmware version information, typically found in System > Status, About, or Firmware sections. Alternatively, check the device startup logs or use the manufacturer's diagnostic tool if available.Affected if The firmware version is lower than 1.1.13166 (e.g., 1.0.x, 1.1.x versions below 1.1.13166).
-
Verify if HTTP web interface is enabledCheck the device network settings through its administrative web interface. Look for the protocol setting (HTTP vs HTTPS) used for the management interface.Affected if The device uses HTTP (port 80) for the administrative interface rather than HTTPS.
-
Check network exposure of the management interfaceDetermine whether the device's web interface is accessible from untrusted networks by reviewing network configuration, firewall rules, and VLAN segmentation. Attempt to access the HTTP interface from an external network if you have authorization to test.Affected if The HTTP management interface is accessible from networks outside the trusted internal network, increasing MITM exposure risk.
-
Inspect authentication trafficIf you have authorization, use a network packet capture tool (such as Wireshark) on the network segment between the client and the device. Initiate a login to the device and examine the HTTP GET request for cleartext password transmission.Affected if The login request shows the password transmitted as a cleartext parameter in the URL or HTTP headers rather than being encrypted or sent over HTTPS.
The device is affected if the firmware version is below 1.1.13166 and the HTTP interface is accessible, allowing passwords to be intercepted in cleartext during authentication.
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 data1.1.13166
Upgrade the Kunbus PR100088 Modbus gateway to Release R02 (Software Version 1.1.13166) or later. Until then, ensure the device is not accessible to untrusted networks and consider network segmentation to reduce MITM exposure risk.
- Consultation4.0 h
- Implementation4.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 $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6531 — 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-6531 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