Summary
A parsing flaw in rsync's auth users directive can silently discard deny rules when an @Group Name entry contains a space. An authenticated user who should be denied based on that group rule may therefore connect to a restricted module.
Affected context
The issue occurs in rsync deployments that use the auth users directive to restrict module access and define denied groups whose names contain spaces. It becomes risky when the affected parser processes these entries using comma-only tokenization, causing the group expression and its deny rule to be interpreted incorrectly.
Exploit preconditions
- Attack surface: Network-accessible rsync module service
- Required access: Valid authentication credentials or another accepted authentication identity
- Trigger point: Parsing the module's
auth usersauthorization list during connection authorization - Why exploitation is possible: A space-containing group entry is split incorrectly, and the associated deny rule can be discarded before access control is evaluated
Why this happens
The vulnerability results from an authorization parser that tokenizes auth users entries only on commas, without preserving group expressions that contain spaces. As a result, an @Group Name deny entry may be divided into separate tokens and lose its intended access-control meaning. This maps to CWE-863: Incorrect Authorization, because the service grants access without correctly enforcing the configured denial rule.
Potential impact
- Authenticated users may access restricted rsync modules
- Protected files or directories could be read
- Authorized write operations could be performed where module permissions allow them
- Data confidentiality or integrity may be reduced
- Misconfigured access boundaries could enable further internal discovery
General mitigation guidance
Mitigation generally focuses on making authorization parsing unambiguous and ensuring deny rules remain intact through validation.
Common defensive patterns include:
- Use a parser that preserves quoted, escaped, or space-containing group expressions according to the configuration grammar
- Validate
auth usersentries against an explicit schema before activating a module - Reject ambiguous or malformed authorization rules rather than silently dropping them
- Apply least privilege to module read and write permissions
- Separate sensitive resources into narrowly scoped modules with independent access policies
- Reduce reliance on broad group-based rules when explicit identity mappings are practical
How teams detect issues like this
Organizations can identify this class of issue through:
- Static analysis of authorization parsers for delimiter handling that conflicts with valid names
- Code review checks for silent token dropping, permissive fallback behavior, and missing parse-error handling
- Regression tests covering group names with spaces and both allow and deny rules
- Configuration linting that verifies every declared denial is represented in the effective policy
- Runtime comparison of configured authorization rules with observed connection decisions
- Policy enforcement that blocks ambiguous access-control syntax during deployment
Automated code review and configuration analysis tools may help surface these patterns.

