Opened at 2014-02-17T00:06:11Z
Closed at 2020-10-30T12:35:44Z
#2192 closed defect (wontfix)
cloud backend: denial of service attacks against XML parser
| Reported by: | daira | Owned by: | daira |
|---|---|---|---|
| Priority: | minor | Milestone: | undecided |
| Component: | code-storage | Version: | cloud-branch |
| Keywords: | DoS cloud-backend s3 security xml | Cc: | |
| Launchpad Bug: |
Description (last modified by daira)
A malicious cloud service could easily cause a DoS against the storage server using some of the attacks described in https://pypi.python.org/pypi/defusedxml/. This is not a particularly serious attack as long as one storage server is associated with each cloud service and that server is running in its own virtual machine, since then the cloud service can only affect its associated storage server's virtual machine. OTOH, switching to a library that prevents these attacks would probably be straightforward.
Change History (5)
comment:1 Changed at 2014-02-17T18:48:32Z by daira
- Keywords cloud-backend s3 added; cloud removed
comment:2 Changed at 2014-02-17T18:48:45Z by daira
- Keywords xml added
comment:3 Changed at 2014-03-07T12:16:51Z by daira
- Description modified (diff)
comment:4 Changed at 2014-03-07T12:17:26Z by daira
- Description modified (diff)
comment:5 Changed at 2020-10-30T12:35:44Z by exarkun
- Resolution set to wontfix
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
The established line of development on the "cloud backend" branch has been abandoned. This ticket is being closed as part of a batch-ticket cleanup for "cloud backend"-related tickets.
If this is a bug, it is probably genuinely no longer relevant. The "cloud backend" branch is too large and unwieldy to ever be merged into the main line of development (particularly now that the Python 3 porting effort is significantly underway).
If this is a feature, it may be relevant to some future efforts - if they are sufficiently similar to the "cloud backend" effort - but I am still closing it because there are no immediate plans for a new development effort in such a direction.
Tickets related to the "leasedb" are included in this set because the "leasedb" code is in the "cloud backend" branch and fairly well intertwined with the "cloud backend". If there is interest in lease implementation change at some future time then that effort will essentially have to be restarted as well.