This can also severely break the UI if a resource is created with a "/" in its name, e.g. a domain. The example in the report below isn't required, just entering "a/b" is sufficient.

Steps to Reproduce:
1. Navigate to Domains in foreman and try to create a new domain. use the following string

你好/`cat /etc/passwd/

2. Note error
3. Attempt to navigate back to main domains UI at all, e.g., server.example.com/foreman/domains

Actual results:

Initial and subsequent errors

"Oops, we're sorry but something went wrong

x No route matches {:action=>"edit", :controller=>"domains", :id=>"你好/`cat /etc/passwd/`"}
If you feel this is an error with Foreman itself, please open a new issue with Foreman ticketing system, You would probably need to attach the Full trace and relevant log entries.

Back"

User cannot access page

Expected results:
Field validation

Workaround: use the CLI or API to remove it.

(https://bugzilla.redhat.com/show_bug.cgi?id=1023093)

PR: https://github.com/theforeman/foreman/pull/988

Applied in changeset 39558b7200a7e1d4d5976ee62e25491d9016e56f.