lwIP - A Lightweight TCP/IP stack - Bugs: bug #46072, ip4addr_aton() does not check the...
You are not allowed to post comments on this tracker with your current authentication level.
bug #46072: ip4addr_aton() does not check the number range of all address parts
Submitter: | April M <april_m> | ||
Submitted: | Tue 29 Sep 2015 06:40:22 AM UTC | ||
Category: | DNS | Severity: | 3 - Normal |
Item Group: | Faulty Behaviour | Status: | Fixed |
Privacy: | Public | Assigned to: | goldsimon |
Open/Closed: | Closed | Planned Release: | None |
lwIP version: | git head |
Wed 30 Sep 2015 12:16:06 PM UTC, comment #4: |
April M <april_m> |
Wed 30 Sep 2015 12:16:00 PM UTC, comment #3: Fixed IPv4, too. Thanks for reporting. |
Simon Goldschmidt <goldsimon> |
Wed 30 Sep 2015 12:07:46 PM UTC, comment #2: IPv6 should be fixed. |
Simon Goldschmidt <goldsimon> |
Wed 30 Sep 2015 11:50:54 AM UTC, comment #1: Actually, lwip_getaddrinfo() is not the problem. Instead, I see two problems:
|
Simon Goldschmidt <goldsimon> |
Tue 29 Sep 2015 06:40:22 AM UTC, original submission:
When using lwip_getaddrinfo() to query strings such as "356.3.4.3" and "1:::1:e:f", it will return 0 indicating successful.
|
April M <april_m> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 5 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2015-09-30 | goldsimon | Status | In Progress | Fixed | |
Open/Closed | Open | Closed | |||
2015-09-30 | goldsimon | Summary | lwip_getaddrinfo() treats invalid IP string as valid | ip4addr_aton() does not check the number range of all address parts | |
2015-09-30 | goldsimon | Status | None | In Progress | |
Assigned to | None | goldsimon |
Powered by Savane 3.13-caa5.
Corresponding source code
Also, IPv6 treats IPv6 string such as ":1:2:3:4:5:6:7:8" or ":1:2::3:4:5:6:7" as valid too.
getaddrinfo() RFC takes IPv4 dot string as valid input when the flag AI_NUMERICHOST is set. In my knowledge, x.x.x.x is the right format of IPv4 dot string, in which x is ranging from 0 to 255.