Project

General

Profile

Actions
Copy link

Bug #19458

closed

Validate the hostname field

Added by Alexis Mousset over 3 years ago. Updated over 1 year ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Security
Target version:
6.1.14
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:

Description

Currently toto " $ <b>tutu</b><script>alert(1);</script>@ is accepted as a valid hostname.

Given the hostname is used in several places, including command arguments, it could be a good thing to restrict its content to a reasonable char set to prevent various injections.

Related issues 2 (0 open — 2 closed)

Related to Rudder - Bug #19456: Lack of HTML escaping in nodes listReleasedNicolas CHARLESActions
Is duplicate of Rudder - Bug #19457: Enforce stricter restriction on authorized node id and hostnameReleasedVincent MEMBRÉActions
Actions
Copy link
 #1

Updated by François ARMAND over 3 years ago

  • Related to Bug #19456: Lack of HTML escaping in nodes list added
Actions
Copy link
 #2

Updated by François ARMAND over 3 years ago

  • Is duplicate of Bug #19457: Enforce stricter restriction on authorized node id and hostname added
Actions
Copy link
 #3

Updated by François ARMAND over 3 years ago

  • Status changed from New to Rejected
Actions
Copy link
 #4

Updated by Alexis Mousset over 1 year ago

  • Private changed from Yes to No
Actions
Copy link

Also available in: Atom PDF