[
https://issues.apache.org/jira/browse/VALIDATOR-419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15866674#comment-15866674
]
Sebb commented on VALIDATOR-419:
--------------------------------
Regarding description point 2):
InetAddress.getByName() permits IPv4 with various leading prefixes.
Also note that RFC 6052 includes examples [1] such as
64:ff9b::192.0.2.33
2001:db8:122:344::192.0.2.33
Therefore Validator should not reject such addresses.
[1] https://tools.ietf.org/html/rfc6052#section-2.4
> Invalid IPv6 addresses that are IPv4-mapped pass InetAddressValidator
> validation
> --------------------------------------------------------------------------------
>
> Key: VALIDATOR-419
> URL: https://issues.apache.org/jira/browse/VALIDATOR-419
> Project: Commons Validator
> Issue Type: Bug
> Components: Routines
> Affects Versions: 1.5.1
> Reporter: Denis Iskhakov
> Priority: Minor
>
> 1) {{InetAddressValidator.getInstance().isValidInet6Address(String
> inet6Address)}} returns {{true}} for value {{0::ffff:192.168.1.1:192.168.1.1}}
> I believe this is due to wrong comparison operand in line #166 of
> InetAddressValidator:
> {code}
> if (index > octets.length - 1 || index > 6) { // CHECKSTYLE IGNORE
> MagicNumber
> // IPV4 occupies last two octets
> return false;
> }
> {code}
> {{index > octets.length - 1}} expression will never be true inside cycle
> {code}for (int index = 0; index < octets.length; index++){code}
> 2) According to https://tools.ietf.org/html/rfc4291 IPv6 address that is
> IPv4-mapped must start with five zero octets followed by one {{ffff}} octet.
> Current implementation of InetAddressValidator does not check this. E.g.
> {{1::2:192.168.1.1}} is considered valid.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
