Cheng XU 974192cd98 Disallow octal format in Ipv4 string ...

In its original specification, leading zero in Ipv4 string is interpreted
as octal literals. So a IP address 0127.0.0.1 actually means 87.0.0.1.

This confusion can lead to many security vulnerabilities. Therefore, in
[IETF RFC 6943], it suggests to disallow octal/hexadecimal format in Ipv4
string all together.

Existing implementation already disallows hexadecimal numbers. This commit
makes Parser reject octal numbers.

Fixes #83648.

[IETF RFC 6943]: https://tools.ietf.org/html/rfc6943#section-3.1.1

2021-03-30 10:24:23 +08:00

..

addr

Remove redundant 'static from library crates

2020-10-18 17:25:51 +02:00

ip

Dont prefix 0x when dbg!(ipv6)

2021-01-20 04:31:34 +00:00

parser

Disallow octal format in Ipv4 string

2021-03-30 10:24:23 +08:00

tcp

std: move "mod tests/benches" to separate files

2020-08-31 02:56:59 +00:00

udp

Use is_ok() instead of empty Ok(_)

2020-10-13 17:01:50 -04:00

addr.rs

Document that the SocketAddr memory representation is not stable

2021-03-26 19:44:06 +01:00

ip.rs

Disallow octal format in Ipv4 string

2021-03-30 10:24:23 +08:00

mod.rs

Use io::Error::new_const everywhere to avoid allocations.

2021-03-21 20:22:38 +01:00

parser.rs

Disallow octal format in Ipv4 string

2021-03-30 10:24:23 +08:00

tcp.rs

Drop support for cloudabi targets

2020-11-22 17:11:41 -05:00

test.rs

mv std libs to library/

2020-07-27 19:51:13 -05:00

udp.rs

Use io::Error::new_const everywhere to avoid allocations.

2021-03-21 20:22:38 +01:00