Closed Bug 91626 Opened 24 years ago Closed 23 years ago

query.cgi javascript fails to escape component names

Categories

(Bugzilla :: Administration, task, P1)

2.12

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: mwrona, Assigned: justdave)

References

Details

- create new component named ' (single quote) - go to query page - type javascript: in your browser URL window and you'll see error: http://xxxxxxx/bugzilla/query.cgi, line 9: unterminated string literal. cpts['''] = new Array(); .......^ The problem is that script(s?) doesn't validate user input accepts such strange names as, e.g. ' or new-line (yes, I managed to do that with mouse copy-paste). IMHO all user input should be trimmed to some well-defined subset of ASCII.
Priority: -- → P1
Target Milestone: --- → Bugzilla 2.16
-> New Bugzilla Product
Assignee: tara → justdave
Component: Bugzilla → Administration
Product: Webtools → Bugzilla
Version: Bugzilla 2.12 → 2.12
See also bug 98181 "/query.cgi doesn't handle single quotes (') in component names".
data validation errors suck. Release blocker... kiko, you're already CCed... this is your department I think. Does your pending javascript patch for the query page fix this already?
Severity: major → blocker
OS: Linux → All
Hardware: PC → All
Summary: Bugzilla fails to prune user input down (at least while entering components) → query.cgi javascript fails to escape component names
*** Bug 98181 has been marked as a duplicate of this bug. ***
I created both a product and a component called ' and nothing broke. It even restored selections properly with bug 97966 fixed locally. Apparently this was fixed by both Gerv's template work and my index-by-number-instead-of-component-name patch to bug 122154. WORKSFORME on the tip.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
clearing milestones on DUPLICATE/WONTFIX/WORKSFORME/INVALID bugs (so they'll show up as needing triage if they get reopened)
Target Milestone: Bugzilla 2.16 → ---
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.