CVE-2020-17470: Input Validation

Published Dec 11, 2020
·
Updated

An issue was discovered in FNET through 4.6.4. The code that initializes the DNS client interface structure does not set sufficiently random transaction IDs (they are always set to 1 in _fnet_dns_poll in fnet_dns.c). This significantly simplifies DNS cache poisoning attacks.

Affected Software

9 affected components
Butok Fnet<=4.6.4
Multiple (open source) uIP-Contiki-OS (end-of-life [EOL]), Version 3.0 and prior
Multiple (open source) uIP-Contiki-NG, Version 4.5 and prior
Multiple (open source) uIP (EOL), Version 1.0 and prior
Multiple (open source) open-iscsi, Version 2.1.12 and prior
Multiple (open source) picoTCP-NG, Version 1.7.0 and prior
Multiple (open source) picoTCP (EOL), Version 1.7.0 and prior
Multiple (open source) FNET, Version 4.6.3
Multiple (open source) Nut/Net, Version 5.1 and prior

Event History

Dec 11, 2020
CVE Published
via MITRE·10:40 PM
Data Sourced
via MITRE·10:40 PM
Description
Data Sourced
11:15 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2020-17470?

The severity of CVE-2020-17470 is considered to be high due to its impact on DNS cache poisoning attacks.

2

How do I fix CVE-2020-17470?

To fix CVE-2020-17470, update FNET to version 4.6.5 or later where the random transaction ID issue has been addressed.

3

What types of software are affected by CVE-2020-17470?

CVE-2020-17470 affects FNET versions up to 4.6.4 and several other open source networking software including uIP, Contiki, and open-iscsi.

4

What specific issue does CVE-2020-17470 exploit?

CVE-2020-17470 exploits the lack of randomness in DNS transaction IDs, making it easier for attackers to perform DNS cache poisoning.

5

Is there a known workaround for CVE-2020-17470?

There are no recommended workarounds for CVE-2020-17470; the best mitigation is to apply the available software update.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203