CVE-2019-1698 json
Cisco IoT Field Network Director XML External Entity Vulnerability
published 7y ago modified 4mo ago also EUVD-2019-10255
- cvss
- 4.9
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.1%
- EPSS 3.1% chance of exploitation in 30 days, percentile 87%
- public exploits
- 0
- none known
Summary
A vulnerability in the web-based user interface of Cisco Internet of Things Field Network Director (IoT-FND) Software could allow an authenticated, remote attacker to gain read access to information that is stored on an affected system. The vulnerability is due to improper handling of XML External Entity (XXE) entries when parsing certain XML files. An attacker could exploit this vulnerability by importing a crafted XML file with malicious entries, which could allow the attacker to read files within the affected application. Versions prior to 4.4(0.26) are affected.
Patch / fix
- Cisco Cisco IoT Field Network Director (IoT-FND) 4.4(0.26)
Is CVE-2019-1698 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 FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
3.12% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 4.9 | CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.0 | 4.9 | CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
Affected products
- Cisco Cisco IoT Field Network Director (IoT-FND)
Classification
- Weakness
-
- CWE-611 Improper Restriction of XML External Entity Reference
References
-
tools.cisco.com
/security/center/content/CiscoSecurityAdvisory/cisco-sa-20190220-iot-fnd-xml
vendor-advisory
-
securityfocus.com
/bid/107093
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2019-1698
- NVD CVE-2019-1698
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.