CVE-2019-6529 json
An attacker could specially craft an FTP request that could crash the PR100088 Modbus gateway versions prior to release R02 (or Software Ve…
published 6y ago modified 4mo ago also EUVD-2019-16088
- cvss
- 4.9
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 63%
- public exploits
- 0
- none known
Summary
An attacker could specially craft an FTP request that could crash the PR100088 Modbus gateway versions prior to release R02 (or Software Version 1.1.13166).
Patch / fix
- kunbus pr100088_modbus_gateway_firmware 1.1.13166
Is CVE-2019-6529 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-19-036-05 updated cvss 4.9
Kunbus PR100088 Modbus Gateway (Update B)
-
Kunbus PR100088 Modbus gateway < R02 (or Software Version 1.1.13166)affected: mitigation “These devices are not intended to be used in a public network. Rather, these devices are intended for use in an industrial environment with a protected network architecture.” kunbus.de
From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf
Exploit prediction
1.01% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:L/Au:S/C:N/I:N/A:C |
Affected products
- n/a PR100088 Modbus gateway
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
ics-cert.us-cert.gov
/advisories/ICSA-19-036-05
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2019-6529
- NVD CVE-2019-6529
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.