mirror of
https://github.com/Hopiu/angular.js.git
synced 2026-03-17 23:40:23 +00:00
$sce is a service that provides Strict Contextual Escaping services to AngularJS. Strict Contextual Escaping -------------------------- Strict Contextual Escaping (SCE) is a mode in which AngularJS requires bindings in certain contexts to result in a value that is marked as safe to use for that context One example of such a context is binding arbitrary html controlled by the user via ng-bind-html-unsafe. We refer to these contexts as privileged or SCE contexts. As of version 1.2, Angular ships with SCE enabled by default. Note: When enabled (the default), IE8 in quirks mode is not supported. In this mode, IE8 allows one to execute arbitrary javascript by the use of the expression() syntax. Refer http://blogs.msdn.com/b/ie/archive/2008/10/16/ending-expressions.aspx to learn more about them. You can ensure your document is in standards mode and not quirks mode by adding <!doctype html> to the top of your HTML document. SCE assists in writing code in way that (a) is secure by default and (b) makes auditing for security vulnerabilities such as XSS, clickjacking, etc. a lot easier. Here's an example of a binding in a privileged context: <input ng-model="userHtml"> <div ng-bind-html-unsafe="{{userHtml}}"> Notice that ng-bind-html-unsafe is bound to {{userHtml}} controlled by the user. With SCE disabled, this application allows the user to render arbitrary HTML into the DIV. In a more realistic example, one may be rendering user comments, blog articles, etc. via bindings. (HTML is just one example of a context where rendering user controlled input creates security vulnerabilities.) For the case of HTML, you might use a library, either on the client side, or on the server side, to sanitize unsafe HTML before binding to the value and rendering it in the document. How would you ensure that every place that used these types of bindings was bound to a value that was sanitized by your library (or returned as safe for rendering by your server?) How can you ensure that you didn't accidentally delete the line that sanitized the value, or renamed some properties/fields and forgot to update the binding to the sanitized value? To be secure by default, you want to ensure that any such bindings are disallowed unless you can determine that something explicitly says it's safe to use a value for binding in that context. You can then audit your code (a simple grep would do) to ensure that this is only done for those values that you can easily tell are safe - because they were received from your server, sanitized by your library, etc. You can organize your codebase to help with this - perhaps allowing only the files in a specific directory to do this. Ensuring that the internal API exposed by that code doesn't markup arbitrary values as safe then becomes a more manageable task. In the case of AngularJS' SCE service, one uses $sce.trustAs (and shorthand methods such as $sce.trustAsHtml, etc.) to obtain values that will be accepted by SCE / privileged contexts. In privileged contexts, directives and code will bind to the result of $sce.getTrusted(context, value) rather than to the value directly. Directives use $sce.parseAs rather than $parse to watch attribute bindings, which performs the $sce.getTrusted behind the scenes on non-constant literals. As an example, ngBindHtmlUnsafe uses $sce.parseAsHtml(binding expression). Here's the actual code (slightly simplified): var ngBindHtmlUnsafeDirective = ['$sce', function($sce) { return function(scope, element, attr) { scope.$watch($sce.parseAsHtml(attr.ngBindHtmlUnsafe), function(value) { element.html(value || ''); }); }; }]; Impact on loading templates --------------------------- This applies both to the ng-include directive as well as templateUrl's specified by directives. By default, Angular only loads templates from the same domain and protocol as the application document. This is done by calling $sce.getTrustedResourceUrl on the template URL. To load templates from other domains and/or protocols, you may either either whitelist them or wrap it into a trusted value. *Please note*: The browser's Same Origin Policy and Cross-Origin Resource Sharing (CORS) policy apply in addition to this and may further restrict whether the template is successfully loaded. This means that without the right CORS policy, loading templates from a different domain won't work on all browsers. Also, loading templates from file:// URL does not work on some browsers. This feels like too much overhead for the developer? ---------------------------------------------------- It's important to remember that SCE only applies to interpolation expressions. If your expressions are constant literals, they're automatically trusted and you don't need to call $sce.trustAs on them. e.g. <div ng-html-bind-unsafe="'<b>implicitly trusted</b>'"></div> just works. Additionally, a[href] and img[src] automatically sanitize their URLs and do not pass them through $sce.getTrusted. SCE doesn't play a role here. The included $sceDelegate comes with sane defaults to allow you to load templates in ng-include from your application's domain without having to even know about SCE. It blocks loading templates from other domains or loading templates over http from an https served document. You can change these by setting your own custom whitelists and blacklists for matching such URLs. This significantly reduces the overhead. It is far easier to pay the small overhead and have an application that's secure and can be audited to verify that with much more ease than bolting security onto an application later.
119 lines
6 KiB
JavaScript
119 lines
6 KiB
JavaScript
'use strict';
|
|
|
|
function $$UrlUtilsProvider() {
|
|
this.$get = [function() {
|
|
var urlParsingNode = document.createElement("a"),
|
|
// NOTE: The usage of window and document instead of $window and $document here is
|
|
// deliberate. This service depends on the specific behavior of anchor nodes created by the
|
|
// browser (resolving and parsing URLs) that is unlikely to be provided by mock objects and
|
|
// cause us to break tests. In addition, when the browser resolves a URL for XHR, it
|
|
// doesn't know about mocked locations and resolves URLs to the real document - which is
|
|
// exactly the behavior needed here. There is little value is mocking these our for this
|
|
// service.
|
|
originUrl = resolve(window.location.href, true);
|
|
|
|
/**
|
|
* @description
|
|
* Normalizes and optionally parses a URL.
|
|
*
|
|
* NOTE: This is a private service. The API is subject to change unpredictably in any commit.
|
|
*
|
|
* Implementation Notes for non-IE browsers
|
|
* ----------------------------------------
|
|
* Assigning a URL to the href property of an anchor DOM node, even one attached to the DOM,
|
|
* results both in the normalizing and parsing of the URL. Normalizing means that a relative
|
|
* URL will be resolved into an absolute URL in the context of the application document.
|
|
* Parsing means that the anchor node's host, hostname, protocol, port, pathname and related
|
|
* properties are all populated to reflect the normalized URL. This approach has wide
|
|
* compatibility - Safari 1+, Mozilla 1+, Opera 7+,e etc. See
|
|
* http://www.aptana.com/reference/html/api/HTMLAnchorElement.html
|
|
*
|
|
* Implementation Notes for IE
|
|
* ---------------------------
|
|
* IE >= 8 and <= 10 normalizes the URL when assigned to the anchor node similar to the other
|
|
* browsers. However, the parsed components will not be set if the URL assigned did not specify
|
|
* them. (e.g. if you assign a.href = "foo", then a.protocol, a.host, etc. will be empty.) We
|
|
* work around that by performing the parsing in a 2nd step by taking a previously normalized
|
|
* URL (e.g. by assining to a.href) and assigning it a.href again. This correctly populates the
|
|
* properties such as protocol, hostname, port, etc.
|
|
*
|
|
* IE7 does not normalize the URL when assigned to an anchor node. (Apparently, it does, if one
|
|
* uses the inner HTML approach to assign the URL as part of an HTML snippet -
|
|
* http://stackoverflow.com/a/472729) However, setting img[src] does normalize the URL.
|
|
* Unfortunately, setting img[src] to something like "javascript:foo" on IE throws an exception.
|
|
* Since the primary usage for normalizing URLs is to sanitize such URLs, we can't use that
|
|
* method and IE < 8 is unsupported.
|
|
*
|
|
* References:
|
|
* http://developer.mozilla.org/en-US/docs/Web/API/HTMLAnchorElement
|
|
* http://www.aptana.com/reference/html/api/HTMLAnchorElement.html
|
|
* http://url.spec.whatwg.org/#urlutils
|
|
* https://github.com/angular/angular.js/pull/2902
|
|
* http://james.padolsey.com/javascript/parsing-urls-with-the-dom/
|
|
*
|
|
* @param {string} url The URL to be parsed.
|
|
* @param {boolean=} parse When true, returns an object for the parsed URL. Otherwise, returns
|
|
* a single string that is the normalized URL.
|
|
* @returns {object|string} When parse is true, returns the normalized URL as a string.
|
|
* Otherwise, returns an object with the following members.
|
|
*
|
|
* | member name | Description |
|
|
* |===============|================|
|
|
* | href | A normalized version of the provided URL if it was not an absolute URL |
|
|
* | protocol | The protocol including the trailing colon |
|
|
* | host | The host and port (if the port is non-default) of the normalizedUrl |
|
|
*
|
|
* These fields from the UrlUtils interface are currently not needed and hence not returned.
|
|
*
|
|
* | member name | Description |
|
|
* |===============|================|
|
|
* | hostname | The host without the port of the normalizedUrl |
|
|
* | pathname | The path following the host in the normalizedUrl |
|
|
* | hash | The URL hash if present |
|
|
* | search | The query string |
|
|
*
|
|
*/
|
|
function resolve(url, parse) {
|
|
var href = url;
|
|
if (msie) {
|
|
// Normalize before parse. Refer Implementation Notes on why this is
|
|
// done in two steps on IE.
|
|
urlParsingNode.setAttribute("href", href);
|
|
href = urlParsingNode.href;
|
|
}
|
|
urlParsingNode.setAttribute('href', href);
|
|
|
|
if (!parse) {
|
|
return urlParsingNode.href;
|
|
}
|
|
// urlParsingNode provides the UrlUtils interface - http://url.spec.whatwg.org/#urlutils
|
|
return {
|
|
href: urlParsingNode.href,
|
|
protocol: urlParsingNode.protocol,
|
|
host: urlParsingNode.host
|
|
// Currently unused and hence commented out.
|
|
// hostname: urlParsingNode.hostname,
|
|
// port: urlParsingNode.port,
|
|
// pathname: urlParsingNode.pathname,
|
|
// hash: urlParsingNode.hash,
|
|
// search: urlParsingNode.search
|
|
};
|
|
}
|
|
|
|
return {
|
|
resolve: resolve,
|
|
/**
|
|
* Parse a request URL and determine whether this is a same-origin request as the application document.
|
|
*
|
|
* @param {string|object} requestUrl The url of the request as a string that will be resolved
|
|
* or a parsed URL object.
|
|
* @returns {boolean} Whether the request is for the same origin as the application document.
|
|
*/
|
|
isSameOrigin: function isSameOrigin(requestUrl) {
|
|
var parsed = (typeof requestUrl === 'string') ? resolve(requestUrl, true) : requestUrl;
|
|
return (parsed.protocol === originUrl.protocol &&
|
|
parsed.host === originUrl.host);
|
|
}
|
|
};
|
|
}];
|
|
}
|