{"id":786,"date":"2013-06-14T10:18:37","date_gmt":"2013-06-14T09:18:37","guid":{"rendered":"https:\/\/securite.intrinsec.com:443\/?p=786"},"modified":"2013-06-14T10:18:37","modified_gmt":"2013-06-14T09:18:37","slug":"html-5-cross-origin-resource-sharing-securiser-communications-interdomaines","status":"publish","type":"post","link":"https:\/\/www.intrinsec.com\/en\/html-5-cross-origin-resource-sharing-securiser-communications-interdomaines\/","title":{"rendered":"HTML5 \u2013 CORS: Securing cross-domain application communications"},"content":{"rendered":"<p><em>As part of its research activities, Intrinsec has focused on the features and risks introduced by the arrival of HTML5. This post discusses Cross-Origin Resource Sharing (CORS), the misuse of which could have a significant impact on the application and the company hosting it.<\/em><\/p>\n<p>Previously, for security reasons, applications from different domains could not communicate bidirectionally. Domain A could send data to domain B, but could not receive a response. More precisely, B did send a response, but the browser rejected it, detecting that it was not an intra-domain communication.<\/p>\n<p>For more information on these intra-domain communications, refer to the W3C Wikipedia page on the <a title=\"SOP\" href=\"http:\/\/www.w3.org\/Security\/wiki\/Same_Origin_Policy\">SOP<\/a>.<\/p>\n<p>The CORS API is implemented in all major browser engines (Gecko 1.9.1, Webkit, Trident 4.0, Presto) and provides various directives via new HTTP headers, including:<\/p>\n<ul>\n<li>\u00ab&quot;Access-Control-Allow-Origin&quot;: this allows you to tell the browser which domains are authorized to receive a response from the server.<\/li>\n<li>\u00ab&quot;Access-Control-Allow-Credentials&quot;: This header indicates whether or not cookies should be transmitted in the response.<\/li>\n<\/ul>\n<p>Note that, for security reasons, it is not possible to set the headers mentioned above to the following values in the same response:<br \/>\n<code>Access-Control-Allow-Origin: *<br \/>\nAccess-Control-Allow-Credentials: true<\/code><\/p>\n<h1>In practical terms, how are these headers used?<\/h1>\n<p>Consider a server &quot;S&quot; whose code is as follows:<br \/>\n<code>&lt;?php<br \/>\nheader(&quot;Access-Control-Allow-Origin: C&quot;);<br \/>\necho &quot;response&quot;;<br \/>\n?&gt;<\/code><\/p>\n<p>and let&#039;s call it customer &quot;C&quot;:<br \/>\n<code>&lt;script&gt;<br \/>\nvar http = new XMLHttpRequest();<br \/>\nhttp.open(&quot;GET&quot;, &quot;S&quot;);<br \/>\nhttp.onload = function() {<br \/>\nvar response = http.responseText;<br \/>\ndocument.write(response);<br \/>\n}<br \/>\nhttp.send();<br \/>\n&lt;\/script&gt;<br \/>\n<\/code><\/p>\n<p>Here, C does receive the response from S since it is among the authorized &quot;origins&quot;.<br \/>\n<a href=\"https:\/\/www.intrinsec.com\/wp-content\/uploads\/2013\/04\/article_intro1.png\"><img fetchpriority=\"high\" decoding=\"async\" class=\"alignnone size-full wp-image-823\" src=\"https:\/\/www.intrinsec.com\/wp-content\/uploads\/2013\/04\/article_intro1.png\" alt=\"\" width=\"492\" height=\"198\" \/><\/a><\/p>\n<h1>Examples of misuse of the Access-Control-Allow-Origin header?<\/h1>\n<h2>Universal authorization<\/h2>\n<p>With the configuration below, the page allows any COR sender to receive a response.<br \/>\n<code>header(&quot;Access-Control-Allow-Origin: *&quot;);<br \/>\n\/\/ actions<\/code><\/p>\n<p>Let&#039;s consider the following scenario: a company has an intranet, accessible only internally, on which the value of the &quot;Access-Control-Allow-Origin&quot; header is set to a <em>wildcard<\/em>. If an employee connects to a malicious site from the company, they could, for example, make an Ajax request to the intranet and receive data from it, via this configuration.<\/p>\n<h3>Conclusion<\/h3>\n<p>If the application has restricted access via some authentication mechanism, it is imperative to assign a specific value to this header. Note, however, that if this is not the case, a wildcard can be used. For these public applications (or portions thereof), the W3C <a title=\"Opening of the CORS\" href=\"http:\/\/www.w3.org\/wiki\/CORS_Enabled\">recommends, moreover <\/a> to \u00abopen them up\u00bb to CORS to allow applications of different natures and authors to communicate with each other.<\/p>\n<h2>Access controlled solely by the Origin header<\/h2>\n<p>Let&#039;s take another example of misuse. The page below displays two different pieces of information depending on the\u2019<em>origin<\/em> of the request. Access to this page is controlled based on the browser&#039;s origin.<\/p>\n<p><code>if (isset($_SERVER[&quot;HTTP_ORIGIN&quot;])) {<br \/>\nif ($_SERVER[&#039;HTTP_ORIGIN&#039;] == &quot;http:\/\/A&quot;) {<br \/>\nheader(&#039;Access-Control-Allow-Origin: http:\/\/A&#039;);<br \/>\necho &quot;Confidential Data&quot;.<br \/>\n}<br \/>\nelse {<br \/>\necho &quot;Denied&quot;.<br \/>\n}<br \/>\n}<\/code><\/p>\n<p>This protection can be bypassed since the Origin header, like any HTTP header, is forgery-able. It should be corrected by only accepting requests that transmit the user&#039;s authenticating cookie (with the <em>Credentials Flag<\/em>, (for Ajax requests, for example). If this cookie is considered valid and if a (valid) token is present, the request can then be processed.<\/p>\n<h1>Attack scenario: &quot;silent&quot; CSRF\u00ab<\/h1>\n<p>Let three protagonists be: a user A having an account on a site B (and therefore a session cookie) and a malicious site O.<br \/>\nThis contains the following script:<br \/>\n<code>request = new XMLHttpRequest();<br \/>\nrequest.open(&quot;GET&quot;,&quot;http:\/\/URL_B\/service.php?buy=apple&quot;,true);<br \/>\nrequest.withCredentials = &quot;true&quot;;<br \/>\nrequest.onreadystatechange = function() {<br \/>\nif (request.readyState == 4) {<br \/>\nvar response = request.responseText;<br \/>\ndocument.getElementById(&quot;response&quot;).textContent = response;<br \/>\n}<br \/>\n}<br \/>\nrequest.send();<\/code><\/p>\n<p>Therefore, as soon as the user visits O, a request will be sent to B, via A. The &quot;withCredentials&quot; attribute is set to <em>true<\/em> This indicates that A&#039;s cookie will be transmitted. Therefore, by executing the &quot;buy&quot; action, a CSRF attack occurred without the user initiating it themselves.<\/p>\n<p><a href=\"https:\/\/www.intrinsec.com\/wp-content\/uploads\/2013\/04\/article_COR_exemple2.jpg\"><img decoding=\"async\" class=\"alignnone size-full wp-image-923\" src=\"https:\/\/www.intrinsec.com\/wp-content\/uploads\/2013\/04\/article_COR_exemple2.jpg\" alt=\"\" width=\"561\" height=\"283\" \/><\/a><\/p>\n<p>One protection from a server perspective against this type of attack is the use of tokens.<\/p>\n<p>As a reminder, a randomly generated token is assigned to a user and stored on the server side, attached to the object representing the user. It is also communicated to the client in cases like the one studied above.<br \/>\nHere, the token would be inserted into the form and, upon validation, the server would verify its authenticity.<\/p>\n<h1>Pentesting<\/h1>\n<p>How can I check if a website or application is vulnerable to Origin impersonation?<br \/>\nFirst, it is necessary to know the value of the Origin header expected by the application. The values of this header and the header are often the same.<br \/>\nIf the two commands below differ in the content of the downloaded file, then the application is vulnerable:<br \/>\n<code>wget --header=&quot;Origin: GoodDomain&quot; URL<br \/>\nwget --header=&quot;Origin: BadDomain&quot; URL<\/code><\/p>\n<p><strong>What are the key takeaways?<\/strong><br \/>\n\u2013 It is strongly advised against using wildcards when there is access restriction;<br \/>\n\u2013 however, if no authentication is required, it is possible to open it via a wildcard;<br \/>\n\u2013 do not rely solely on the Origin header: use a system of cookies and tokens;<\/p>\n<h1>References<\/h1>\n<p><a title=\"On the safety of the CORS\" href=\"http:\/\/code.google.com\/p\/html5security\/wiki\/CrossOriginRequestSecurity\">On the safety of the CORS<\/a><br \/>\n<a title=\"Silent CSRF\" href=\"http:\/\/evil-bit.blogspot.fr\/2012\/07\/html5-xhr-and-silent-csrf.html\">Silent CSRF<\/a><\/p>","protected":false},"excerpt":{"rendered":"<p>As part of its research activities, Intrinsec focused on the functionalities and risks [\u2026]<\/p>","protected":false},"author":1,"featured_media":1061,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[92,93,94],"class_list":["post-786","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-non-categorise","tag-cors","tag-cross-origin-resource-sharing","tag-html5"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.0 (Yoast SEO v27.8) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>HTML5 - CORS : S\u00e9curiser les communications applicatives interdomaines - INTRINSEC<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.intrinsec.com\/en\/html-5-cross-origin-resource-sharing-securiser-communications-interdomaines\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"HTML5 - CORS : S\u00e9curiser les communications applicatives interdomaines\" \/>\n<meta property=\"og:description\" content=\"Dans le cadre de ses activit\u00e9s de recherche, Intrinsec s&rsquo;est int\u00e9ress\u00e9 aux fonctionnalit\u00e9s et risques [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.intrinsec.com\/en\/html-5-cross-origin-resource-sharing-securiser-communications-interdomaines\/\" \/>\n<meta property=\"og:site_name\" content=\"INTRINSEC\" \/>\n<meta property=\"article:published_time\" content=\"2013-06-14T09:18:37+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.intrinsec.com\/wp-content\/uploads\/2025\/03\/About-Us-Subscribe-BG.webp\" \/>\n\t<meta property=\"og:image:width\" content=\"681\" \/>\n\t<meta property=\"og:image:height\" content=\"694\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/webp\" \/>\n<meta name=\"author\" content=\"Intrinsec\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@Intrinsec\" \/>\n<meta name=\"twitter:site\" content=\"@Intrinsec\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Intrinsec\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.intrinsec.com\\\/html-5-cross-origin-resource-sharing-securiser-communications-interdomaines\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.intrinsec.com\\\/html-5-cross-origin-resource-sharing-securiser-communications-interdomaines\\\/\"},\"author\":{\"name\":\"Intrinsec\",\"@id\":\"https:\\\/\\\/www.intrinsec.com\\\/#\\\/schema\\\/person\\\/ade590fbc7ad6f413727bae7cd3fb799\"},\"headline\":\"HTML5 &#8211; CORS : S\u00e9curiser les communications applicatives interdomaines\",\"datePublished\":\"2013-06-14T09:18:37+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.intrinsec.com\\\/html-5-cross-origin-resource-sharing-securiser-communications-interdomaines\\\/\"},\"wordCount\":888,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/www.intrinsec.com\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.intrinsec.com\\\/html-5-cross-origin-resource-sharing-securiser-communications-interdomaines\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.intrinsec.com\\\/wp-content\\\/uploads\\\/2025\\\/03\\\/About-Us-Subscribe-BG.webp\",\"keywords\":[\"cors\",\"cross-origin resource sharing\",\"html5\"],\"articleSection\":[\"Non cat\u00e9goris\u00e9\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.intrinsec.com\\\/html-5-cross-origin-resource-sharing-securiser-communications-interdomaines\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.intrinsec.com\\\/html-5-cross-origin-resource-sharing-securiser-communications-interdomaines\\\/\",\"url\":\"https:\\\/\\\/www.intrinsec.com\\\/html-5-cross-origin-resource-sharing-securiser-communications-interdomaines\\\/\",\"name\":\"HTML5 - CORS : S\u00e9curiser les communications applicatives interdomaines - INTRINSEC\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.intrinsec.com\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.intrinsec.com\\\/html-5-cross-origin-resource-sharing-securiser-communications-interdomaines\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.intrinsec.com\\\/html-5-cross-origin-resource-sharing-securiser-communications-interdomaines\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.intrinsec.com\\\/wp-content\\\/uploads\\\/2025\\\/03\\\/About-Us-Subscribe-BG.webp\",\"datePublished\":\"2013-06-14T09:18:37+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.intrinsec.com\\\/html-5-cross-origin-resource-sharing-securiser-communications-interdomaines\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.intrinsec.com\\\/html-5-cross-origin-resource-sharing-securiser-communications-interdomaines\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.intrinsec.com\\\/html-5-cross-origin-resource-sharing-securiser-communications-interdomaines\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.intrinsec.com\\\/wp-content\\\/uploads\\\/2025\\\/03\\\/About-Us-Subscribe-BG.webp\",\"contentUrl\":\"https:\\\/\\\/www.intrinsec.com\\\/wp-content\\\/uploads\\\/2025\\\/03\\\/About-Us-Subscribe-BG.webp\",\"width\":681,\"height\":694},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.intrinsec.com\\\/html-5-cross-origin-resource-sharing-securiser-communications-interdomaines\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/www.intrinsec.com\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"HTML5 &#8211; CORS : S\u00e9curiser les communications applicatives interdomaines\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.intrinsec.com\\\/#website\",\"url\":\"https:\\\/\\\/www.intrinsec.com\\\/\",\"name\":\"INTRINSEC\",\"description\":\"Notre m\u00e9tier , Prot\u00e9ger le v\u00f4tre\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.intrinsec.com\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.intrinsec.com\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.intrinsec.com\\\/#organization\",\"name\":\"INTRINSEC\",\"alternateName\":\"ISEC\",\"url\":\"https:\\\/\\\/www.intrinsec.com\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.intrinsec.com\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.intrinsec.com\\\/wp-content\\\/uploads\\\/2025\\\/02\\\/libellule.png\",\"contentUrl\":\"https:\\\/\\\/www.intrinsec.com\\\/wp-content\\\/uploads\\\/2025\\\/02\\\/libellule.png\",\"width\":1322,\"height\":1322,\"caption\":\"INTRINSEC\"},\"image\":{\"@id\":\"https:\\\/\\\/www.intrinsec.com\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/x.com\\\/Intrinsec\",\"https:\\\/\\\/fr.linkedin.com\\\/company\\\/intrinsec\",\"https:\\\/\\\/www.youtube.com\\\/channel\\\/UC0trUZAHNZOUbxYnNdecM4A\"],\"description\":\"soci\u00e9t\u00e9 de consulting, pure player cybers\u00e9curit\u00e9 fran\u00e7ais et europ\u00e9en depuis plus de 30ans, sp\u00e9cialiste dans la s\u00e9curit\u00e9 offensive & audit (pentest\\\/red team), GRC, et services IMSS comme le SOC, CTI et CERT Intrinsec est qualifi\u00e9 PASSI Elev\u00e9, PRIS Elev\u00e9 et PACS par l'ANSSI\",\"email\":\"contact@intrinsec.com\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.intrinsec.com\\\/#\\\/schema\\\/person\\\/ade590fbc7ad6f413727bae7cd3fb799\",\"name\":\"Intrinsec\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/fde6ed961c7078765b03a213927b5c4001b1cef4787255188f5b502a99e6ddd6?s=96&d=retro&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/fde6ed961c7078765b03a213927b5c4001b1cef4787255188f5b502a99e6ddd6?s=96&d=retro&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/fde6ed961c7078765b03a213927b5c4001b1cef4787255188f5b502a99e6ddd6?s=96&d=retro&r=g\",\"caption\":\"Intrinsec\"},\"sameAs\":[\"https:\\\/\\\/www.intrinsec.com\"],\"url\":\"https:\\\/\\\/www.intrinsec.com\\\/en\\\/author\\\/ufhtbqccsz\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"HTML5 - CORS: Securing inter-domain application communications - INTRINSEC","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.intrinsec.com\/en\/html-5-cross-origin-resource-sharing-securiser-communications-interdomaines\/","og_locale":"en_US","og_type":"article","og_title":"HTML5 - CORS : S\u00e9curiser les communications applicatives interdomaines","og_description":"Dans le cadre de ses activit\u00e9s de recherche, Intrinsec s&rsquo;est int\u00e9ress\u00e9 aux fonctionnalit\u00e9s et risques [&hellip;]","og_url":"https:\/\/www.intrinsec.com\/en\/html-5-cross-origin-resource-sharing-securiser-communications-interdomaines\/","og_site_name":"INTRINSEC","article_published_time":"2013-06-14T09:18:37+00:00","og_image":[{"width":681,"height":694,"url":"https:\/\/www.intrinsec.com\/wp-content\/uploads\/2025\/03\/About-Us-Subscribe-BG.webp","type":"image\/webp"}],"author":"Intrinsec","twitter_card":"summary_large_image","twitter_creator":"@Intrinsec","twitter_site":"@Intrinsec","twitter_misc":{"Written by":"Intrinsec","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.intrinsec.com\/html-5-cross-origin-resource-sharing-securiser-communications-interdomaines\/#article","isPartOf":{"@id":"https:\/\/www.intrinsec.com\/html-5-cross-origin-resource-sharing-securiser-communications-interdomaines\/"},"author":{"name":"Intrinsec","@id":"https:\/\/www.intrinsec.com\/#\/schema\/person\/ade590fbc7ad6f413727bae7cd3fb799"},"headline":"HTML5 &#8211; CORS : S\u00e9curiser les communications applicatives interdomaines","datePublished":"2013-06-14T09:18:37+00:00","mainEntityOfPage":{"@id":"https:\/\/www.intrinsec.com\/html-5-cross-origin-resource-sharing-securiser-communications-interdomaines\/"},"wordCount":888,"commentCount":0,"publisher":{"@id":"https:\/\/www.intrinsec.com\/#organization"},"image":{"@id":"https:\/\/www.intrinsec.com\/html-5-cross-origin-resource-sharing-securiser-communications-interdomaines\/#primaryimage"},"thumbnailUrl":"https:\/\/www.intrinsec.com\/wp-content\/uploads\/2025\/03\/About-Us-Subscribe-BG.webp","keywords":["cors","cross-origin resource sharing","html5"],"articleSection":["Non cat\u00e9goris\u00e9"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.intrinsec.com\/html-5-cross-origin-resource-sharing-securiser-communications-interdomaines\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.intrinsec.com\/html-5-cross-origin-resource-sharing-securiser-communications-interdomaines\/","url":"https:\/\/www.intrinsec.com\/html-5-cross-origin-resource-sharing-securiser-communications-interdomaines\/","name":"HTML5 - CORS: Securing inter-domain application communications - INTRINSEC","isPartOf":{"@id":"https:\/\/www.intrinsec.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.intrinsec.com\/html-5-cross-origin-resource-sharing-securiser-communications-interdomaines\/#primaryimage"},"image":{"@id":"https:\/\/www.intrinsec.com\/html-5-cross-origin-resource-sharing-securiser-communications-interdomaines\/#primaryimage"},"thumbnailUrl":"https:\/\/www.intrinsec.com\/wp-content\/uploads\/2025\/03\/About-Us-Subscribe-BG.webp","datePublished":"2013-06-14T09:18:37+00:00","breadcrumb":{"@id":"https:\/\/www.intrinsec.com\/html-5-cross-origin-resource-sharing-securiser-communications-interdomaines\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.intrinsec.com\/html-5-cross-origin-resource-sharing-securiser-communications-interdomaines\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.intrinsec.com\/html-5-cross-origin-resource-sharing-securiser-communications-interdomaines\/#primaryimage","url":"https:\/\/www.intrinsec.com\/wp-content\/uploads\/2025\/03\/About-Us-Subscribe-BG.webp","contentUrl":"https:\/\/www.intrinsec.com\/wp-content\/uploads\/2025\/03\/About-Us-Subscribe-BG.webp","width":681,"height":694},{"@type":"BreadcrumbList","@id":"https:\/\/www.intrinsec.com\/html-5-cross-origin-resource-sharing-securiser-communications-interdomaines\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.intrinsec.com\/"},{"@type":"ListItem","position":2,"name":"HTML5 &#8211; CORS : S\u00e9curiser les communications applicatives interdomaines"}]},{"@type":"WebSite","@id":"https:\/\/www.intrinsec.com\/#website","url":"https:\/\/www.intrinsec.com\/","name":"INTRINSEC","description":"Our job is to protect yours.","publisher":{"@id":"https:\/\/www.intrinsec.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.intrinsec.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.intrinsec.com\/#organization","name":"INTRINSEC","alternateName":"ISEC","url":"https:\/\/www.intrinsec.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.intrinsec.com\/#\/schema\/logo\/image\/","url":"https:\/\/www.intrinsec.com\/wp-content\/uploads\/2025\/02\/libellule.png","contentUrl":"https:\/\/www.intrinsec.com\/wp-content\/uploads\/2025\/02\/libellule.png","width":1322,"height":1322,"caption":"INTRINSEC"},"image":{"@id":"https:\/\/www.intrinsec.com\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/x.com\/Intrinsec","https:\/\/fr.linkedin.com\/company\/intrinsec","https:\/\/www.youtube.com\/channel\/UC0trUZAHNZOUbxYnNdecM4A"],"description":"Intrinsec, a consulting firm and pure-play French and European cybersecurity provider for over 30 years, specializes in offensive security and auditing (penetration testing\/red teams), GRC, and IMSS services such as SOC, CTI, and CERT. Intrinsec is qualified at PASSI High, PRIS High, and PACS levels by ANSSI.","email":"contact@intrinsec.com"},{"@type":"Person","@id":"https:\/\/www.intrinsec.com\/#\/schema\/person\/ade590fbc7ad6f413727bae7cd3fb799","name":"Intrinsic","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/fde6ed961c7078765b03a213927b5c4001b1cef4787255188f5b502a99e6ddd6?s=96&d=retro&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/fde6ed961c7078765b03a213927b5c4001b1cef4787255188f5b502a99e6ddd6?s=96&d=retro&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/fde6ed961c7078765b03a213927b5c4001b1cef4787255188f5b502a99e6ddd6?s=96&d=retro&r=g","caption":"Intrinsec"},"sameAs":["https:\/\/www.intrinsec.com"],"url":"https:\/\/www.intrinsec.com\/en\/author\/ufhtbqccsz\/"}]}},"_links":{"self":[{"href":"https:\/\/www.intrinsec.com\/en\/wp-json\/wp\/v2\/posts\/786","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.intrinsec.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.intrinsec.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.intrinsec.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.intrinsec.com\/en\/wp-json\/wp\/v2\/comments?post=786"}],"version-history":[{"count":0,"href":"https:\/\/www.intrinsec.com\/en\/wp-json\/wp\/v2\/posts\/786\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.intrinsec.com\/en\/wp-json\/wp\/v2\/media\/1061"}],"wp:attachment":[{"href":"https:\/\/www.intrinsec.com\/en\/wp-json\/wp\/v2\/media?parent=786"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.intrinsec.com\/en\/wp-json\/wp\/v2\/categories?post=786"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.intrinsec.com\/en\/wp-json\/wp\/v2\/tags?post=786"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}