Actions
Bug #16725
open
Improper input validation in filter field
Status:
New
Priority:
Normal
Assignee:
-
Category:
mDNS Bridge
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
Affected Architecture:
All
Description
There seems to be over aggressive input validation on the inbound/outbound allow/deny filter fields.
Service names can have special characters and spaces '2AB601BC6BD9@Localhost'._raop._tcp.local. or 'Bedroom TV'._airplay._tcp.local. as per [RFC6763](https://datatracker.ietf.org/doc/html/rfc6763#section-4.1.1).
Due to the filter matching design in mdns-bridge, labels must match exactly and do not support substring matching.
Entering one of these service names in the webgui gives an "Invalid domain" error and yet they are valid.
Manually modifying the configuration file works and directly validates that the issue is with webgui for the package.
No data to display
Actions