{"id":208344,"date":"2023-08-29T14:10:15","date_gmt":"2023-08-29T14:10:15","guid":{"rendered":"https:\/\/www.ninjaone.com\/script-hub\/comment-mitiger-cve-2023-36884-powershell\/"},"modified":"2024-03-04T16:02:56","modified_gmt":"2024-03-04T16:02:56","slug":"comment-mitiger-cve-2023-36884-powershell","status":"publish","type":"script_hub","link":"https:\/\/www.ninjaone.com\/fr\/script-hub\/comment-mitiger-cve-2023-36884-powershell\/","title":{"rendered":"Faille zero-day Microsoft non corrig\u00e9e : Comment mitiger CVE-2023-36884 avec PowerShell"},"content":{"rendered":"<p>Les mises \u00e0 jour du Patch Tuesday de juillet 2023 de Microsoft ont mis en \u00e9vidence plusieurs vuln\u00e9rabilit\u00e9s activement exploit\u00e9es, dont une (ou plusieurs ?) qui n&rsquo;a toujours pas \u00e9t\u00e9 corrig\u00e9e. Voici ce que vous devez savoir sur\u00a0<a href=\"https:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2023-36884\" target=\"_blank\" rel=\"noopener\">CVE-2023-36884<\/a>, une vuln\u00e9rabilit\u00e9 zero-day que les attaquants exploitent pour obtenir une ex\u00e9cution de code \u00e0 distance via des documents Microsoft Office \u00ab\u00a0sp\u00e9cialement fabriqu\u00e9s\u00a0\u00bb.<\/p>\n<h2>Qu&rsquo;est-ce que CVE-2023-36884 ?<\/h2>\n<p>R\u00e9ponse courte : <a href=\"https:\/\/msrc.microsoft.com\/update-guide\/vulnerability\/CVE-2023-36884\" target=\"_blank\" rel=\"noopener\">Microsoft caract\u00e9rise CVE-2023-36884<\/a> comme une vuln\u00e9rabilit\u00e9 d&rsquo;ex\u00e9cution de code HTML \u00e0 distance pour Office et Windows avec un CVSS de 8,3. R\u00e9ponse plus substantielle : Pour l&rsquo;instant, Microsoft est toujours en train d&rsquo;enqu\u00eater activement, et ne fournit pas grand-chose au-del\u00e0 d&rsquo;une description superficielle. Elle indique qu&rsquo;une exploitation r\u00e9ussie de la vuln\u00e9rabilit\u00e9 peut permettre \u00e0 un attaquant d&rsquo;ex\u00e9cuter du code \u00e0 distance en utilisant le contexte de la victime, et qu&rsquo;il suffit de la tromper pour qu&rsquo;elle ouvre un document Microsoft Office con\u00e7u \u00e0 cette fin. Curieusement, le communiqu\u00e9 commence par indiquer que \u00ab\u00a0Microsoft enqu\u00eate sur des rapports faisant \u00e9tat d&rsquo;une <strong>s\u00e9rie\u00a0<\/strong>de vuln\u00e9rabilit\u00e9s d&rsquo;ex\u00e9cution de code \u00e0 distance\u00a0\u00bb, ce qui am\u00e8ne <a href=\"https:\/\/twitter.com\/wdormann\/status\/1678922526905233408?s=20\" target=\"_blank\" rel=\"noopener\">Will Dormann, expert en vuln\u00e9rabilit\u00e9s, \u00e0 \u00e9mettre la th\u00e9orie suivante<\/a> : \u00ab\u00a0CVE-2023-36884 n&rsquo;est qu&rsquo;un espace r\u00e9serv\u00e9 pour une mise \u00e0 jour visant \u00e0 corriger plusieurs vuln\u00e9rabilit\u00e9s par le biais d&rsquo;une seule CVE, qui pourrait \u00eatre publi\u00e9e ult\u00e9rieurement, \u00e0 une date inconnue.\u00a0\u00bb Le communiqu\u00e9 manque de pr\u00e9cisions mais il comporte un lien vers un <a href=\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2023\/07\/11\/storm-0978-attacks-reveal-financial-and-espionage-motives\/\" target=\"_blank\" rel=\"noopener\">article de blog<\/a> qui explique comment Microsoft l&rsquo;a d\u00e9couvert.<\/p>\n<h2>Espionnage et ransomware : exploitation active de CVE-2023-36884<\/h2>\n<p>En Juin, <a href=\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2023\/07\/11\/storm-0978-attacks-reveal-financial-and-espionage-motives\/\" target=\"_blank\" rel=\"noopener\">Microsoft a identifi\u00e9<\/a> une campagne de phishing lanc\u00e9e par un pirate que Microsoft suit sous le nom de Storm-0978. La campagne a cibl\u00e9 des entit\u00e9s gouvernementales et de d\u00e9fense en Am\u00e9rique du Nord et en Europe, avec des app\u00e2ts li\u00e9s au Congr\u00e8s Mondial Ukrainien. Les e-mails envoy\u00e9s dans le cadre de cette campagne contenaient des liens vers des documents Word qui exploitaient la norme CVE-2023-36884 afin d&rsquo;installer des portes d\u00e9rob\u00e9es. Alors que ces cibles et les activit\u00e9s post-compromission sugg\u00e8rent des intentions d&rsquo;espionnage, Microsoft note que, pendant que cette campagne se d\u00e9roulait, elle a \u00e9galement d\u00e9couvert que Storm-0978 menait des attaques de ransomware distinctes sur des cibles sans rapport avec elle, en utilisant les m\u00eames \u00e9l\u00e9ments. Selon Microsoft, l&rsquo;activit\u00e9 du pirate en mati\u00e8re de ransomware a \u00e9t\u00e9 \u00ab\u00a0essentiellement de nature opportuniste et n&rsquo;a absolument rien \u00e0 voir avec les cibles d&rsquo;espionnage\u00a0\u00bb. MISE \u00c0 JOUR : Une <a href=\"https:\/\/blogs.blackberry.com\/en\/2023\/07\/romcom-targets-ukraine-nato-membership-talks-at-nato-summit\" target=\"_blank\" rel=\"noopener\">analyse technique encore plus approfondie de cette campagne<\/a> est disponible sur le site de BlackBerry.<\/p>\n<h2>Existe-t-il un correctif pour CVE-2023-36884 ?<\/h2>\n<p>Pour l&rsquo;instant, non. Microsoft indique qu&rsquo;elle continue d&rsquo;enqu\u00eater activement sur cette vuln\u00e9rabilit\u00e9 et qu&rsquo;\u00e0 l&rsquo;issue de cette enqu\u00eate, la soci\u00e9t\u00e9 \u00ab\u00a0prendra les mesures appropri\u00e9es pour prot\u00e9ger ses clients. Il peut s&rsquo;agir de fournir une mise \u00e0 jour de s\u00e9curit\u00e9 dans le cadre de notre processus de publication mensuel ou de fournir une mise \u00e0 jour de s\u00e9curit\u00e9 hors cycle, en fonction des besoins du client.\u00a0\u00bb<\/p>\n<h2>Mesures de mitigation pour CVE-2023-36884<\/h2>\n<p><a href=\"https:\/\/msrc.microsoft.com\/update-guide\/vulnerability\/CVE-2023-36884\" target=\"_blank\" rel=\"noopener\">Selon Microsoft<\/a>, les entreprises disposent actuellement de trois moyens pour se prot\u00e9ger :<\/p>\n<ol>\n<li>Les clients qui utilisent Microsoft Defender pour Office sont prot\u00e9g\u00e9s contre les pi\u00e8ces jointes qui tentent d&rsquo;exploiter cette vuln\u00e9rabilit\u00e9.<\/li>\n<li>Dans les cha\u00eenes d&rsquo;attaque actuelles, l&rsquo;utilisation de la r\u00e8gle de r\u00e9duction de la surface d&rsquo;attaque <a href=\"https:\/\/learn.microsoft.com\/en-us\/microsoft-365\/security\/defender-endpoint\/attack-surface-reduction-rules-reference?view=o365-worldwide#block-all-office-applications-from-creating-child-processes\" target=\"_blank\" rel=\"noopener\">\u00a0\u00ab\u00a0Bloquer la cr\u00e9ation de processus fils pour toutes les applications Office\u00a0\u00bb<\/a>\u00a0 emp\u00eachera l&rsquo;exploitation de la vuln\u00e9rabilit\u00e9.<\/li>\n<li>Les entreprises qui ne peuvent pas profiter de ces protections peuvent ajouter les noms d&rsquo;application suivants \u00e0 cette cl\u00e9 de registre en tant que valeurs de type REG_DWORD avec des donn\u00e9es 1. : ComputerHKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftInternet ExplorerMainFeatureControlFEATURE_BLOCK_CROSS_PROTOCOL_FILE_NAVIGATION<\/li>\n<\/ol>\n<ul>\n<li style=\"list-style-type: none;\">\n<ul>\n<li>Excel.exe<\/li>\n<li>Graph.exe<\/li>\n<li>MSAccess.exe<\/li>\n<li>MSPub.exe<\/li>\n<li>PowerPoint.exe<\/li>\n<li>Visio.exe<\/li>\n<li>WinProj.exe<\/li>\n<li>WinWord.exe<\/li>\n<li>Wordpad.exe<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p style=\"padding-left: 40px;\"><strong>Remarque : <\/strong>Microsoft indique que si ces param\u00e8tres de registre peuvent att\u00e9nuer l&rsquo;exploitation de la faille,\u00a0, ils pourraient \u00e9galement affecter le fonctionnement normal de certains cas d&rsquo;utilisation li\u00e9s \u00e0 ces applications. Il est donc important de tester les changements avant de les d\u00e9ployer \u00e0 grande \u00e9chelle.<\/p>\n<h2>Comment mitiger les effets de CVE-2023-36884\u00a0\u00e0 l&rsquo;aide de PowerShell<\/h2>\n<p>Pour ceux qui envisagent de modifier le registre,\u00a0, notre ing\u00e9nieur produit logiciel Kyle Bohlander a cr\u00e9\u00e9 le script suivant qui automatise le processus. L&rsquo;utilisation de ce script avec NinjaOne (ou le <a href=\"https:\/\/www.g2.com\/categories\/remote-monitoring-management-rmm\" target=\"_blank\" rel=\"noopener\">RMM de votre choix<\/a>) vous permettra de <a href=\"https:\/\/www.ninjaone.com\/fr\/plateforme-de-gestion-des-correctifs\/windows\/\">d\u00e9ployer la mitigation \u00e0 distance<\/a> et \u00e0 <a href=\"https:\/\/www.ninjaone.com\/webinar\/secrets-to-painless-patching-at-scale\/\">grande \u00e9chelle<\/a>. <strong>Remarque :<\/strong> Ce script n&rsquo;est pas r\u00e9serv\u00e9 aux utilisateurs de NinjaOne. Il peut \u00eatre utilis\u00e9 par tout le monde. Toutefois, comme le conseille Microsoft, ce correctif doit \u00eatre d\u00e9ploy\u00e9 sur des machines de test avant d&rsquo;\u00eatre d\u00e9ploy\u00e9 \u00e0 plus grande \u00e9chelle. Comme d&rsquo;habitude, si vous d\u00e9cidez de l&rsquo;ex\u00e9cuter, cela est \u00e0 vos risques et p\u00e9rils. <strong>Exigences de l&rsquo;appareil : <\/strong>Fonctionne sur les syst\u00e8mes Windows 7 et Windows Server 2008 ou ult\u00e9rieurs. <strong>Si vous devez revenir en arri\u00e8re :<\/strong> Les param\u00e8tres de la cl\u00e9 de registre peuvent \u00eatre annul\u00e9s \u00e0 l&rsquo;aide du param\u00e8tre -Undo, ou appliqu\u00e9s \u00e0 des produits Office sp\u00e9cifiques \u00e0 l&rsquo;aide du param\u00e8tre -OfficeProducts.<\/p>\n<blockquote><p><img decoding=\"async\" class=\"alignleft size-thumbnail wp-image-162511\" src=\"https:\/\/www.ninjaone.com\/wp-content\/uploads\/2024\/02\/kyle-bohlander-80x80-1.png\" alt=\"\" width=\"80\" height=\"80\" \/>Auteur du script : <strong><a href=\"https:\/\/www.linkedin.com\/in\/kyle-bohlander\/\" target=\"_blank\" rel=\"noopener\">Kyle Bohlander<\/a>, Ing\u00e9nieur produit logiciel chez NinjaOne<\/strong><\/p><\/blockquote>\n<p><a href=\"https:\/\/go.ninjaone.com\/l\/652283\/2023-07-13\/4dhscy\/652283\/1689270503D3a9HKAS\/CVE_2023_36844.ps1\" target=\"_blank\" rel=\"noopener\">T\u00e9l\u00e9chargez le fichier de script ici<\/a>.<br \/>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\">&lt;#\r\n.SYNOPSIS\r\n    This script will set the registry keys required to remediate CVE-2023-36884. Please note that these keys may effect regular functionality of Microsoft Office Products. \r\n    These changes can be undone with the -Undo parameter or applied only to specific office products using the -OfficeProducts parameter.\r\n.DESCRIPTION\r\n    This script will set the registry keys required to remediate CVE-2023-36884. Please note that these keys may effect regular functionality of Microsoft Office Products. \r\n    These changes can be undone with the -Undo parameter or applied only to specific office products using the -OfficeProducts parameter.\r\n.EXAMPLE\r\n    (No Parameters)\r\n    \r\n    Visio was selected for remediation.\r\n    Set Registry::HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftInternet ExplorerMainFeatureControlFEATURE_BLOCK_CROSS_PROTOCOL_FILE_NAVIGATIONVisio.exe to 1\r\n    Success!\r\n    Word was selected for remediation.\r\n    Set Registry::HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftInternet ExplorerMainFeatureControlFEATURE_BLOCK_CROSS_PROTOCOL_FILE_NAVIGATIONWinWord.exe to 1\r\n    Success!\r\n    Wordpad was selected for remediation.\r\n    Set Registry::HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftInternet ExplorerMainFeatureControlFEATURE_BLOCK_CROSS_PROTOCOL_FILE_NAVIGATIONWordpad.exe to 1\r\n    Success!\r\n    Project was selected for remediation.\r\n    Set Registry::HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftInternet ExplorerMainFeatureControlFEATURE_BLOCK_CROSS_PROTOCOL_FILE_NAVIGATIONWinProj.exe to 1\r\n    Success!\r\n    PowerPoint was selected for remediation.\r\n    Set Registry::HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftInternet ExplorerMainFeatureControlFEATURE_BLOCK_CROSS_PROTOCOL_FILE_NAVIGATIONPowerPoint.exe to 1\r\n    Success!\r\n    Excel was selected for remediation.\r\n    Set Registry::HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftInternet ExplorerMainFeatureControlFEATURE_BLOCK_CROSS_PROTOCOL_FILE_NAVIGATIONExcel.exe to 1\r\n    Success!\r\n    Publisher was selected for remediation.\r\n    Set Registry::HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftInternet ExplorerMainFeatureControlFEATURE_BLOCK_CROSS_PROTOCOL_FILE_NAVIGATIONMsPub.exe to 1\r\n    Success!\r\n    Graph was selected for remediation.\r\n    Set Registry::HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftInternet ExplorerMainFeatureControlFEATURE_BLOCK_CROSS_PROTOCOL_FILE_NAVIGATIONGraph.exe to 1\r\n    Success!\r\n    Access was selected for remediation.\r\n    Set Registry::HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftInternet ExplorerMainFeatureControlFEATURE_BLOCK_CROSS_PROTOCOL_FILE_NAVIGATIONMSAccess.exe to 1\r\n    Success!\r\n\u200b\r\nPARAMETER: -Undo\r\n    Remove's the registry keys used for this fix (if they're set at all).\r\n.EXAMPLE\r\n    -Undo\r\n    \r\n    Visio was selected for remediation.\r\n    Succesfully removed registry key!\r\n    Word was selected for remediation.\r\n    Succesfully removed registry key!\r\n    Wordpad was selected for remediation.\r\n    Succesfully removed registry key!\r\n    Project was selected for remediation.\r\n    Succesfully removed registry key!\r\n    PowerPoint was selected for remediation.\r\n    Succesfully removed registry key!\r\n    Excel was selected for remediation.\r\n    Succesfully removed registry key!\r\n    Publisher was selected for remediation.\r\n    Succesfully removed registry key!\r\n    Graph was selected for remediation.\r\n    Succesfully removed registry key!\r\n    Access was selected for remediation.\r\n    Succesfully removed registry key!\r\n\u200b\r\nPARAMETER: -OfficeProducts \"Excel,Word\"\r\n    Set's the registry key for only those products. Can be given an individual product or a comma seperated list. Can also be used in combination with the -Undo parameter Ex. \"Publisher\" or \"Word,Excel,Access\"\r\n.EXAMPLE\r\n    -OfficeProducts \"Excel,Word\"\r\n    \r\n    Word was selected for remediation.\r\n    Set Registry::HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftInternet ExplorerMainFeatureControlFEATURE_BLOCK_CROSS_PROTOCOL_FILE_NAVIGATIONWinWord.exe to 1\r\n    Success!\r\n    Excel was selected for remediation.\r\n    Set Registry::HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftInternet ExplorerMainFeatureControlFEATURE_BLOCK_CROSS_PROTOCOL_FILE_NAVIGATIONExcel.exe to 1\r\n    Success!\r\n\u200b\r\n.OUTPUTS\r\n    None\r\n.NOTES\r\n    General notes\r\n#&gt;\r\n[CmdletBinding()]\r\nparam (\r\n    [Parameter()]\r\n    [String]$OfficeProducts = \"All\",\r\n    [Parameter()]\r\n    [Switch]$Undo\r\n)\r\n\u200b\r\nbegin {\r\n\u200b\r\n    # Test's if the script is running in an elevated fashion (required for HKLM edits)\r\n    function Test-IsElevated {\r\n        $id = [System.Security.Principal.WindowsIdentity]::GetCurrent()\r\n        $p = New-Object System.Security.Principal.WindowsPrincipal($id)\r\n        $p.IsInRole([System.Security.Principal.WindowsBuiltInRole]::Administrator)\r\n    }\r\n\u200b\r\n    # This is just to make setting regkey's easier\r\n    function Set-RegKey {\r\n        param (\r\n            $Path,\r\n            $Name,\r\n            $Value,\r\n            [ValidateSet(\"DWord\", \"QWord\", \"String\", \"ExpandedString\", \"Binary\", \"MultiString\", \"Unknown\")]\r\n            $PropertyType = \"DWord\"\r\n        )\r\n        if (-not $(Test-Path -Path $Path)) {\r\n            # Check if path does not exist and create the path\r\n            New-Item -Path $Path -Force | Out-Null\r\n        }\r\n        if ((Get-ItemProperty -Path $Path -Name $Name -ErrorAction SilentlyContinue)) {\r\n            # Update property and print out what it was changed from and changed to\r\n            $CurrentValue = (Get-ItemProperty -Path $Path -Name $Name -ErrorAction SilentlyContinue).$Name\r\n            try {\r\n                Set-ItemProperty -Path $Path -Name $Name -Value $Value -Force -Confirm:$false -ErrorAction Stop | Out-Null\r\n            }\r\n            catch {\r\n                Write-Error \"[Error] Unable to Set registry key for $Name please see below error!\"\r\n                Write-Error $_\r\n                exit 1\r\n            }\r\n            Write-Host \"$Path$Name changed from $CurrentValue to $($(Get-ItemProperty -Path $Path -Name $Name -ErrorAction SilentlyContinue).$Name)\"\r\n        }\r\n        else {\r\n            # Create property with value\r\n            try {\r\n                New-ItemProperty -Path $Path -Name $Name -Value $Value -PropertyType $PropertyType -Force -Confirm:$false -ErrorAction Stop | Out-Null\r\n            }\r\n            catch {\r\n                Write-Error \"[Error] Unable to Set registry key for $Name please see below error!\"\r\n                Write-Error $_\r\n                exit 1\r\n            }\r\n            Write-Host \"Set $Path$Name to $($(Get-ItemProperty -Path $Path -Name $Name -ErrorAction SilentlyContinue).$Name)\"\r\n        }\r\n    }\r\n\u200b\r\n    # All the microsoft office products with their corresponding dword value\r\n    $RemediationValues = @{ \"Excel\" = \"Excel.exe\"; \"Graph\" = \"Graph.exe\"; \"Access\" = \"MSAccess.exe\"; \"Publisher\" = \"MsPub.exe\"; \"PowerPoint\" = \"PowerPnt.exe\"; \"OldPowerPoint\" = \"PowerPoint.exe\" ; \"Visio\" = \"Visio.exe\"; \"Project\" = \"WinProj.exe\"; \"Word\" = \"WinWord.exe\"; \"Wordpad\" = \"Wordpad.exe\" }\r\n}\r\nprocess {\r\n\u200b\r\n    # Error out when not elevated\r\n    if (-not (Test-IsElevated)) {\r\n        Write-Error -Message \"Access Denied. Please run with Administrator privileges.\"\r\n        exit 1\r\n    }\r\n\u200b\r\n    # If they have a smaller selection we'll want to filter our remediation list\r\n    if ($OfficeProducts -notlike \"All\") {\r\n        $OfficeProducts = $OfficeProducts.split(',') | ForEach-Object { $_.Trim() }\r\n        $RemediationTargets = $RemediationValues.GetEnumerator() | ForEach-Object { $_ | Where-Object { $OfficeProducts -match $_.Key } }\r\n    }\r\n    else {\r\n        $RemediationTargets = $RemediationValues.GetEnumerator()\r\n    }\r\n\u200b\r\n    # Path to all the registry keys\r\n    $Path = \"Registry::HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftInternet ExplorerMainFeatureControlFEATURE_BLOCK_CROSS_PROTOCOL_FILE_NAVIGATION\"\r\n\u200b\r\n    # We'll want to display an error if we don't have anything to do\r\n    if ($RemediationTargets) { \r\n\u200b\r\n        # For Each product we're targeting we'll set the regkey. The Set-RegKey function already checks if it was succesful and will display an error and exit if it fails\r\n        $RemediationTargets | ForEach-Object { \r\n            Write-Host \"$($_.Name) was selected for remediation.\"\r\n            if (-not $Undo) {\r\n                Set-RegKey -Path $Path -Name $_.Value -Value 1\r\n                Write-Host \"Success!\"\r\n            }\r\n            else {\r\n                # If you only applied it to certain products this will error so instead we'll hide the errors and check afterwards if the registry key is there.\r\n                Remove-ItemProperty -Path $Path -Name $_.Value -ErrorAction SilentlyContinue | Out-Null\r\n                if (Get-ItemProperty -Path $Path -Name $_.Value -ErrorAction SilentlyContinue) {\r\n                    Write-Error \"[Error] Unable to undo registry key $($_.Value)!\"\r\n                    exit 1\r\n                }\r\n                else {\r\n                    Write-Host \"Succesfully removed registry key!\"\r\n                }\r\n            }\r\n        }\r\n\u200b\r\n        Write-Warning \"A reboot may be required.\"\r\n        exit 0\r\n    }\r\n    else {\r\n        Write-Host $RemediationTargets\r\n        Write-Warning \"No products were selected! The valid value's for -OfficeProducts is listed below you can also use a comma seperated list or simply put 'All'.\"\r\n        $RemediationValues | Sort-Object Name | Format-Table | Out-String | Write-Host\r\n        Write-Error \"ERROR: Nothing to do!\"\r\n        exit 1\r\n    }\r\n}<\/pre>\n<p>&nbsp;<\/p>\n<\/p>\n","protected":false},"author":28,"featured_media":140556,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"_relevanssi_hide_post":"","_relevanssi_hide_content":"","_relevanssi_pin_for_all":"","_relevanssi_pin_keywords":"","_relevanssi_unpin_keywords":"","_relevanssi_related_keywords":"","_relevanssi_related_include_ids":"","_relevanssi_related_exclude_ids":"","_relevanssi_related_no_append":"","_relevanssi_related_not_related":"","_relevanssi_related_posts":"","_relevanssi_noindex_reason":"","_lmt_disableupdate":"no","_lmt_disable":""},"operating_system":[4212],"use_cases":[4284],"class_list":["post-208344","script_hub","type-script_hub","status-publish","has-post-thumbnail","hentry","script_hub_category-windows"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.ninjaone.com\/fr\/wp-json\/wp\/v2\/script_hub\/208344","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.ninjaone.com\/fr\/wp-json\/wp\/v2\/script_hub"}],"about":[{"href":"https:\/\/www.ninjaone.com\/fr\/wp-json\/wp\/v2\/types\/script_hub"}],"author":[{"embeddable":true,"href":"https:\/\/www.ninjaone.com\/fr\/wp-json\/wp\/v2\/users\/28"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ninjaone.com\/fr\/wp-json\/wp\/v2\/comments?post=208344"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.ninjaone.com\/fr\/wp-json\/wp\/v2\/media\/140556"}],"wp:attachment":[{"href":"https:\/\/www.ninjaone.com\/fr\/wp-json\/wp\/v2\/media?parent=208344"}],"wp:term":[{"taxonomy":"script_hub_category","embeddable":true,"href":"https:\/\/www.ninjaone.com\/fr\/wp-json\/wp\/v2\/operating_system?post=208344"},{"taxonomy":"use_cases","embeddable":true,"href":"https:\/\/www.ninjaone.com\/fr\/wp-json\/wp\/v2\/use_cases?post=208344"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}