Project

General

Profile

Actions

Bug #9584

closed
JP JP

Potential XSS in services_acb.php via hostname parameter with legacy settings

Bug #9584: Potential XSS in services_acb.php via hostname parameter with legacy settings

Added by Jim Pingle over 7 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Backup / Restore
Target version:
Start date:
06/13/2019
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
All
Affected Architecture:
All

Description

If legacy settings are configured in ACB, there is a potential XSS vector in services_acb.php via the hostname parameter which is printed back to the user without encoding.

To reproduce, setup legacy settings in ACB and then load a URL such as https://x.x.x.x/services_acb.php?hostname=%3Cscript%3Ealert(0);%3C/script%3E&legacy=true

JP Updated by Jim Pingle over 7 years ago Actions #1

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

Applied in changeset commit:fe482ccc1eaf59137b29008bc040faaad25088f0.

JP Updated by Jim Pingle about 7 years ago Actions #2

  • Status changed from Feedback to Resolved

Legacy options are moot now, they have been removed.

JP Updated by Jim Pingle almost 7 years ago Actions #3

  • Target version changed from 2.5.0 to 2.4.5

JP Updated by Jim Pingle almost 7 years ago Actions #4

  • Status changed from Resolved to Feedback

Needs checked and/or tested again on 2.4.5 snapshots

JP Updated by Jim Pingle over 6 years ago Actions #5

  • Status changed from Feedback to Resolved

The affected code has been completely removed from 2.4.5 and later, so this has become moot.

JP Updated by Jim Pingle over 6 years ago Actions #6

  • Private changed from Yes to No
Actions

Also available in: Atom