If I create a vpp-acl rule without specifying port ranges:
(example request in postman attachments)

then VAT acl_dump shows:
sport 0-0 dport 0-0

while configuring the same thing through VAT:
acl_add_replace ipv4 permit src 192.168.0.0/24 dst 192.168.1.0/24

will result in:
sport 0-65535 dport 0-65535

The full range of ports. Note that port 0 is real, just reserved.
Although I cannot test this with packets, as the underlying functionality isn't there yet.