ISSUE-154: Security approach
Security approach
- State:
- CLOSED
- Product:
- Network Service Discovery
- Raised by:
- Frederick Hirsch
- Opened on:
- 2013-10-02
- Description:
- on behalf of Youenn Fablet
http://lists.w3.org/Archives/Public/public-device-apis/2013Sep/0029.html
In case the WG is not aware, implementation of the NSD API was discussed on various browser engine mailing lists ([1], [2], [3]).
Interesting feedback related to security issues was brought up.
First, fingerprint issues were raised.
These issues may probably be solved by user permission requests and/or data exposure minimization.
Second, a granted local service is exposed to receiving and processing any kind of data from a given web page.
Local services are often weak in terms of security (not regularly patched for instance, [4]).
This may enable new hacking possibilities through tweaked HTTP requests (XML/SOAP payloads or arbitrary data e.g.).
Solving both kinds of issues through a single user permission UI was perceived as too complex and error-prone.
>From what I know, research has been done on identifying issues related to protocols and implementations like SSDP.
Since the browser engine is handling the discovery part, the NSD API spec is probably safe there.
I do not know much about the possibilities on hacking through tweaked HTTP requests.
This potential threat, especially for legacy devices, weakens the idea of whitelisting granted local services.
Also, getting access to a discovered local service can already be done using existing approaches:
- packaged web applications/extensions may get permissions to do cross-origin requests
- CORS may be implemented in future local network services
The discovery part of the NSD API specification seems already in a pretty good shape.
The access granting part of the NSD API specification may take more time to mature.
Given all of that, would it make sense to split the NSD API specification in two documents?
Regards,
Youenn
[1] https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/HT0KZKuTLxM
[2] http://www.mail-archive.com/webkit-dev@lists.webkit.org/msg23727.html
[3] https://bugzilla.mozilla.org/show_bug.cgi?id=914579
[4] http://www.upnp-hacks.org/ - Related Actions Items:
- No related actions
- Related emails:
- [admin] Agenda - Distributed Meeting 15 May 2014 (from frederick.hirsch@nokia.com on 2014-05-12)
- [admin] Agenda - Distributed Meeting 27 March 2014 (from Frederick.Hirsch@nokia.com on 2014-03-27)
- [admin] Agenda - Distributed Meeting 20 March 2014 (from Frederick.Hirsch@nokia.com on 2014-03-19)
- [admin] Cancel teleconference 6 March, next call 20 March (from Frederick.Hirsch@nokia.com on 2014-03-05)
- Re: [admin] Agenda - Distributed Meeting 27 February 2014 (from dom@w3.org on 2014-02-27)
- [admin] Agenda - Distributed Meeting 27 February 2014 (from Frederick.Hirsch@nokia.com on 2014-02-26)
- [admin] Agenda - Distributed Meeting 20 February 2014 (from Frederick.Hirsch@nokia.com on 2014-02-18)
- [admin] Agenda - Distributed Meeting 13 February 2014 (resend corrected date) (from Frederick.Hirsch@nokia.com on 2014-02-13)
- [admin] Agenda - Distributed Meeting 12 February 2014 (from Frederick.Hirsch@nokia.com on 2014-02-13)
- Network Service Discovery API (from alexander.adolf@condition-alpha.com on 2014-02-12)
- [admin] Agenda - Distributed Meeting 6 February 2014 (from Frederick.Hirsch@nokia.com on 2014-02-05)
- Regrets: [admin] Agenda - Distributed Meeting 30 January 2014 (from dom@w3.org on 2014-01-29)
- [admin] Agenda - Distributed Meeting 30 January 2014 (from Frederick.Hirsch@nokia.com on 2014-01-28)
- [admin] Agenda - Distributed Meeting 16 January 2014 (from Frederick.Hirsch@nokia.com on 2014-01-15)
- [admin] Agenda - Distributed Meeting 9 January 2014 (from Frederick.Hirsch@nokia.com on 2014-01-08)
- [admin] Agenda - Distributed Meeting 12 December2013 (from Frederick.Hirsch@nokia.com on 2013-12-11)
- Re: [admin] Agenda - Distributed Meeting 21 November 2013 (from jean-claude.dufourd@telecom-paristech.fr on 2013-11-21)
- [admin] Agenda - Distributed Meeting 21 November 2013 (from Frederick.Hirsch@nokia.com on 2013-11-21)
- Agenda - Distributed Meeting 7 November 2013 (Thursday) (from Frederick.Hirsch@nokia.com on 2013-11-05)
- Re: Agenda - Distributed Meeting 31 October 2013 (Thursday) (from jean-claude.dufourd@telecom-paristech.fr on 2013-10-29)
- Agenda - Distributed Meeting 31 October 2013 (Thursday) (from Frederick.Hirsch@nokia.com on 2013-10-28)
- Re: Agenda - Distributed Meeting 17 October 2013 (Thursday) (from jean-claude.dufourd@telecom-paristech.fr on 2013-10-17)
- Re: Agenda - Distributed Meeting 17 October 2013 (Thursday) (from dom@w3.org on 2013-10-17)
- Agenda - Distributed Meeting 17 October 2013 (Thursday) (from Frederick.Hirsch@nokia.com on 2013-10-17)
- Agenda - Distributed Meeting 10 October 2013 (Thursday) (from Frederick.Hirsch@nokia.com on 2013-10-10)
- Draft minutes today 3 October 2013 (from Frederick.Hirsch@nokia.com on 2013-10-03)
- Agenda - Distributed Meeting 3 October 2013 (Thursday) (from Frederick.Hirsch@nokia.com on 2013-10-02)
- DAP-ISSUE-154: Security approach [Network Service Discovery] (from sysbot+tracker@w3.org on 2013-10-02)
Related notes:
Proposal and comment from Rich, http://lists.w3.org/Archives/Public/public-device-apis/2013Sep/0040.html
Support for CORS based approach from Dom, http://lists.w3.org/Archives/Public/public-device-apis/2013Sep/0041.html
http://lists.w3.org/Archives/Public/public-device-apis/2013Sep/0043.html
Making CORS work, Rich, http://lists.w3.org/Archives/Public/public-device-apis/2013Sep/0045.html
more CORS support, Sony/Claes, http://lists.w3.org/Archives/Public/public-device-apis/2013Sep/0059.html
more CORS support, AT&T/Bin http://lists.w3.org/Archives/Public/public-device-apis/2013Sep/0064.html
Display change log