diff options
| author | bors <bors@rust-lang.org> | 2021-03-30 19:34:23 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2021-03-30 19:34:23 +0000 |
| commit | 74874a690bc95443292496ff5df5cc5c8cb56e0b (patch) | |
| tree | a544dc9228430c48b01336887f08720f0b44e9cb /compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp | |
| parent | 926ec1cb8b81ac47ba2e5b8a6780e95d39241afa (diff) | |
| parent | 974192cd98b3efca8e5cd293f641f561e7487b30 (diff) | |
| download | rust-74874a690bc95443292496ff5df5cc5c8cb56e0b.tar.gz rust-74874a690bc95443292496ff5df5cc5c8cb56e0b.zip | |
Auto merge of #83652 - xu-cheng:ipv4-octal, r=sfackler
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
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp')
0 files changed, 0 insertions, 0 deletions