<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Matthieu Destrez, Author at OVHcloud Blog</title>
	<atom:link href="https://blog.ovhcloud.com/author/matthieu-destrezovhcloud-com/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.ovhcloud.com/author/matthieu-destrezovhcloud-com/</link>
	<description>Innovation for Freedom</description>
	<lastBuildDate>Mon, 15 May 2023 09:36:59 +0000</lastBuildDate>
	<language>en-GB</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://blog.ovhcloud.com/wp-content/uploads/2019/07/cropped-cropped-nouveau-logo-ovh-rebranding-32x32.gif</url>
	<title>Matthieu Destrez, Author at OVHcloud Blog</title>
	<link>https://blog.ovhcloud.com/author/matthieu-destrezovhcloud-com/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Vulnerability on Veeam Backup &#038; Replication</title>
		<link>https://blog.ovhcloud.com/vulnerability-on-veeam-backup-replication/</link>
		
		<dc:creator><![CDATA[Matthieu Destrez]]></dc:creator>
		<pubDate>Mon, 15 May 2023 08:13:47 +0000</pubDate>
				<category><![CDATA[Accelerating with OVHcloud]]></category>
		<guid isPermaLink="false">https://blog.ovhcloud.com/?p=25292</guid>

					<description><![CDATA[On the 7th of match, VEEAM has released a kb describing a new CVE on several software provided by the company. This vulnerability may result in credentials leak and remote code execution. VEEAM is a software company specialized in the resilience of virtualization infrastructures and cloud based applications. The principal software, VEEAM Backup &#38; Replication [&#8230;]<img src="//blog.ovhcloud.com/wp-content/plugins/matomo/app/matomo.php?idsite=1&amp;rec=1&amp;url=https%3A%2F%2Fblog.ovhcloud.com%2Fvulnerability-on-veeam-backup-replication%2F&amp;action_name=Vulnerability%20on%20Veeam%20Backup%20%26amp%3B%20Replication&amp;urlref=https%3A%2F%2Fblog.ovhcloud.com%2Ffeed%2F" style="border:0;width:0;height:0" width="0" height="0" alt="" />]]></description>
										<content:encoded><![CDATA[
<p>On the 7th of match, VEEAM has released a <a href="https://www.veeam.com/kb4424" data-wpel-link="external" target="_blank" rel="nofollow external noopener noreferrer">kb</a> describing a new CVE on several software provided by the company. This vulnerability may result in credentials leak and remote code execution.</p>



<p>VEEAM is a software company specialized in the resilience of virtualization infrastructures and cloud based applications. The principal software, VEEAM Backup &amp; Replication provides a backup solution for virtual machines, physical servers, cloud infrastructure or applications. It supports several types of backup repositories to store backup (CIFS, S3 bucket, &#8230;). </p>



<figure class="wp-block-image aligncenter size-large is-resized"><img fetchpriority="high" decoding="async" src="https://blog.ovhcloud.com/wp-content/uploads/2023/05/IMG_1526-1024x538.jpg" alt="Vulnerability on Veeam Backup &amp; Replication" class="wp-image-25336" width="512" height="269" srcset="https://blog.ovhcloud.com/wp-content/uploads/2023/05/IMG_1526-1024x538.jpg 1024w, https://blog.ovhcloud.com/wp-content/uploads/2023/05/IMG_1526-300x158.jpg 300w, https://blog.ovhcloud.com/wp-content/uploads/2023/05/IMG_1526-768x404.jpg 768w, https://blog.ovhcloud.com/wp-content/uploads/2023/05/IMG_1526.jpg 1199w" sizes="(max-width: 512px) 100vw, 512px" /></figure>



<h3 class="wp-block-heading">VEEAM in OVHcloud</h3>



<p>At OVHcloud, there are many ways to consume VEEAM software:</p>



<ul class="wp-block-list">
<li>The first one is the Veeam Backup Managed option of Hosted Private Cloud. OVHcloud fully manage this solution and so, we already applied the mitigation related to this vulnerability.</li>



<li>The second one is to install a backup server and use the Veeam Enterprise (proposed by OVHcloud) option to get a VEEAM License. In this Option, License is billed with a pay as you go billing. In this configuration you can use all features available in Veeam Backup &amp; Replication and fully manage the infrastructure</li>



<li>The last one is to install a backup Server and bring your own license. In this configuration you fully manage the backup infrastructure. </li>
</ul>



<p>In the last two options, you can add Hosted private clouds, dedicated servers and other services in the VEEAM Backup &amp; Replication software. </p>



<p>The CVE-2023-27532 affects to Veeam.Backup.Service.exe listening on TCP 9401 port of VEEAM servers. It allows an unauthenticated user to request credentials stored in VEEAM database but also to remotely execute commands on the Backup Server. The Attacker may use those credentials to gain access to any servers protected by the backup software.</p>



<h3 class="wp-block-heading">Exploit scenario</h3>



<p>Even if it is not trivial to exploit this vulnerability, at least one ransomware organization actively exploits it, and many exploit codes are publicly available. Therefore there is a serious concern that automated attacks number increase in the next few weeks. </p>



<p>In the operating method observed, the attacker exploits the CVE to get the credentials of the infrastructure covered by the backup solution (ie: vSphere credentials, …) in order to remove all virtual machines from the inventory and finally encrypts all backups. Then, he will ask for a ransom to get the encryption key. For now, we only identified this exploit on Backup Servers or Backup Proxies running Windows operating system where the port 9401 directly exposed on The Internet.</p>



<figure class="wp-block-image size-large"><img decoding="async" width="1024" height="423" src="https://blog.ovhcloud.com/wp-content/uploads/2023/05/Untitled-2023-05-10-1040-1024x423.png" alt="" class="wp-image-25275" srcset="https://blog.ovhcloud.com/wp-content/uploads/2023/05/Untitled-2023-05-10-1040-1024x423.png 1024w, https://blog.ovhcloud.com/wp-content/uploads/2023/05/Untitled-2023-05-10-1040-300x124.png 300w, https://blog.ovhcloud.com/wp-content/uploads/2023/05/Untitled-2023-05-10-1040-768x317.png 768w, https://blog.ovhcloud.com/wp-content/uploads/2023/05/Untitled-2023-05-10-1040.png 1403w" sizes="(max-width: 1024px) 100vw, 1024px" /></figure>



<h3 class="wp-block-heading">How to know if my server is vulnerable</h3>



<p>All Releases of VEEAM Backup &amp; Replication earlier than 12.0.0.1420 P20230223 or 11.0.1.1261 P20230227 are vulnerable. If untrusted IPs can reach the port 9401, the service is vulnerable.</p>



<h3 class="wp-block-heading">Solution &amp; Mitigation</h3>



<p>In order to protect your infrastructure, we highly recommend to update your backup software. You can find patched binaries in the <a href="https://www.veeam.com/kb4424" data-wpel-link="external" target="_blank" rel="nofollow external noopener noreferrer">official documentation</a>. </p>



<p>Waiting for the update, and to prevent future vulnerabilities exposition, we recommend to apply the following configuration:</p>



<p>At first, We highly recommend to avoid exposing Backup Infrastructure directly on unsecured networks (Internet, ..,).</p>



<p>When you install VEEAM on a server, it will configure the firewall to allow any connection on VEEAM ports without restriction on Remote address. All ports are so directly reachable from everywhere.</p>



<figure class="wp-block-gallery has-nested-images columns-default is-cropped wp-block-gallery-1 is-layout-flex wp-block-gallery-is-layout-flex">
<figure class="wp-block-image size-large is-style-default"><img decoding="async" width="1024" height="506" data-id="25280" src="https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-091122-1-1024x506.png" alt="" class="wp-image-25280" srcset="https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-091122-1-1024x506.png 1024w, https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-091122-1-300x148.png 300w, https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-091122-1-768x379.png 768w, https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-091122-1.png 1213w" sizes="(max-width: 1024px) 100vw, 1024px" /></figure>
</figure>



<p>We recommend to apply firewall rules to restrict the ports to the strict minimum of hosts.</p>



<p>To do so, make sure the Windows Defender Firewall is set to block any inbound connections that does not match a rule.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="619" height="436" src="https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-091729.png" alt="" class="wp-image-25281" srcset="https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-091729.png 619w, https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-091729-300x211.png 300w" sizes="auto, (max-width: 619px) 100vw, 619px" /></figure>



<p>Then, make sure all ports used are only reachable from servers you trust. For an optimal configuration refers to the <a href="https://helpcenter.veeam.com/docs/backup/vsphere/used_ports.html?ver=120" data-wpel-link="external" target="_blank" rel="nofollow external noopener noreferrer">official documentation.</a></p>



<figure class="wp-block-gallery has-nested-images columns-default is-cropped wp-block-gallery-2 is-layout-flex wp-block-gallery-is-layout-flex">
<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="745" height="586" data-id="25284" src="https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-092900.png" alt="" class="wp-image-25284" srcset="https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-092900.png 745w, https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-092900-300x236.png 300w" sizes="auto, (max-width: 745px) 100vw, 745px" /></figure>
</figure>



<p>You should see the firewall rule is now restricted to the IPs you configured.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1019" height="42" src="https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-093148-1.png" alt="" class="wp-image-25286" srcset="https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-093148-1.png 1019w, https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-093148-1-300x12.png 300w, https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-093148-1-768x32.png 768w" sizes="auto, (max-width: 1019px) 100vw, 1019px" /></figure>



<p>Finally, if you are not using the mount server, we recommend to totally block totally the port 9401.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="92" src="https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-092654-1024x92.png" alt="" class="wp-image-25283" srcset="https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-092654-1024x92.png 1024w, https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-092654-300x27.png 300w, https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-092654-768x69.png 768w, https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-092654.png 1063w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p>Unfortunately, as the exploit is using legit access, There is no possible mitigation at virtualization infrastructure or backup repositories level. Therefore, It is essential to guarantee the security of components using those infrastructures.</p>



<h3 class="wp-block-heading">If you get compromised</h3>



<p>If you think you have been compromised, we highly recommend to contact OVHcloud support as soon as possible in order to evaluate solutions to maybe recover your data.</p>



<h3 class="wp-block-heading">Additional links:</h3>



<p><a href="https://www.veeam.com/kb4424" data-wpel-link="external" target="_blank" rel="nofollow external noopener noreferrer">https://www.veeam.com/kb4424</a><br><a href="https://helpcenter.veeam.com/docs/backup/vsphere/used_ports.html?ver=120" data-wpel-link="external" target="_blank" rel="nofollow external noopener noreferrer">https://helpcenter.veeam.com/docs/backup/vsphere/used_ports.html?ver=120</a></p>



<p><a href="https://www.ovhcloud.com/fr/enterprise/products/hosted-private-cloud/" data-wpel-link="external" target="_blank" rel="nofollow external noopener noreferrer">https://www.ovhcloud.com/fr/enterprise/products/hosted-private-cloud/</a><br><a href="https://www.ovhcloud.com/fr/enterprise/products/hosted-private-cloud/veeam-backup-managed/" data-wpel-link="external" target="_blank" rel="nofollow external noopener noreferrer">https://www.ovhcloud.com/fr/enterprise/products/hosted-private-cloud/veeam-backup-managed/</a><br><a href="https://www.ovhcloud.com/fr/storage-solutions/veeam-enterprise/" data-wpel-link="external" target="_blank" rel="nofollow external noopener noreferrer">https://www.ovhcloud.com/fr/storage-solutions/veeam-enterprise/</a></p>
<img loading="lazy" decoding="async" src="//blog.ovhcloud.com/wp-content/plugins/matomo/app/matomo.php?idsite=1&amp;rec=1&amp;url=https%3A%2F%2Fblog.ovhcloud.com%2Fvulnerability-on-veeam-backup-replication%2F&amp;action_name=Vulnerability%20on%20Veeam%20Backup%20%26amp%3B%20Replication&amp;urlref=https%3A%2F%2Fblog.ovhcloud.com%2Ffeed%2F" style="border:0;width:0;height:0" width="0" height="0" alt="" />]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Vulnérabilité sur VEEAM Backup &#038; Replication</title>
		<link>https://blog.ovhcloud.com/vulnerabilite-sur-veeam-backup-replication/</link>
		
		<dc:creator><![CDATA[Matthieu Destrez]]></dc:creator>
		<pubDate>Mon, 15 May 2023 08:06:47 +0000</pubDate>
				<category><![CDATA[OVHcloud en Français]]></category>
		<guid isPermaLink="false">https://blog.ovhcloud.com/?p=25274</guid>

					<description><![CDATA[Le 7 mars 2023, la société VEEAM publiait dans son KB4424 une vulnérabilité sur différents logiciels fournis par l’entreprise. Cette vulnérabilité peut déboucher sur la fuite d’identifiants ainsi que sur l’exécution de code à distance. La société VEEAM est un éditeur logiciel spécialisé dans la résilience des infrastructures de virtualisation et des application cloud. Son [&#8230;]<img src="//blog.ovhcloud.com/wp-content/plugins/matomo/app/matomo.php?idsite=1&amp;rec=1&amp;url=https%3A%2F%2Fblog.ovhcloud.com%2Fvulnerabilite-sur-veeam-backup-replication%2F&amp;action_name=Vuln%C3%A9rabilit%C3%A9%20sur%20VEEAM%20Backup%20%26amp%3B%20Replication&amp;urlref=https%3A%2F%2Fblog.ovhcloud.com%2Ffeed%2F" style="border:0;width:0;height:0" width="0" height="0" alt="" />]]></description>
										<content:encoded><![CDATA[
<p>Le 7 mars 2023, la société VEEAM publiait dans son <a href="https://www.veeam.com/kb4424" data-wpel-link="external" target="_blank" rel="nofollow external noopener noreferrer">KB4424</a> une vulnérabilité sur différents logiciels fournis par l’entreprise. Cette vulnérabilité peut déboucher sur la fuite d’identifiants ainsi que sur l’exécution de code à distance.</p>



<p>La société VEEAM est un éditeur logiciel spécialisé dans la résilience des infrastructures de virtualisation et des application cloud. Son principal logiciel, Veeam Backup &amp; Replication permet la sauvegarde de machines virtuelles, de serveurs physiques, d’infrastructures cloud ou encore d’applications. Les sauvegardes sont stockés dans différents types de stockages de destinations.</p>



<figure class="wp-block-image aligncenter size-large is-resized"><img loading="lazy" decoding="async" src="https://blog.ovhcloud.com/wp-content/uploads/2023/05/IMG_1525-1024x538.jpg" alt="Vulnérabilité sur VEEAM Backup &amp; Replication" class="wp-image-25324" width="512" height="269" srcset="https://blog.ovhcloud.com/wp-content/uploads/2023/05/IMG_1525-1024x538.jpg 1024w, https://blog.ovhcloud.com/wp-content/uploads/2023/05/IMG_1525-300x158.jpg 300w, https://blog.ovhcloud.com/wp-content/uploads/2023/05/IMG_1525-768x404.jpg 768w, https://blog.ovhcloud.com/wp-content/uploads/2023/05/IMG_1525.jpg 1199w" sizes="auto, (max-width: 512px) 100vw, 512px" /></figure>



<h2 class="wp-block-heading">Utiilisation de VEEAM chez OVHcloud</h2>



<p>Chez OVHcloud, il existe plusieurs contextes dans lesquels les logiciels VEEAM peuvent être utilisés :</p>



<ul class="wp-block-list">
<li>L’option Veeam Backup Managed du produit Hosted Private Cloud est basée sur les solutions veeam. La solution étant entièrement gérée par OVHcloud, les mitigations nécessaires ont été appliquées par OVHcloud.</li>



<li>L’option Veeam Enterprise du produit Hosted Private Cloud vous permet d’installer et de gérer votre serveur de sauvegarde. Vous profitez donc de toutes les fonctionnalités des applications Veeam. Dans cette option, OVHcloud vous permet d’obtenir la licence Veeam et d’avoir une facturation en Pay-as-you-go. La gestion du serveur et de la sécurité de l’infrastructure de backup est donc de la responsabilité de notre client.</li>



<li>L’installation d’un serveur de sauvegarde avec vos propres licences. Dans ce mode, vous avez la main sur la totalité de votre infrastructure de backup.</li>
</ul>



<p>Dans ces deux derniers modes, il vous est possible d’ajouter dans votre solution de sauvegarde, des Hosted Private Cloud, des serveurs dédiés, ainsi que d’autres services.</p>



<p>La CVE-2023-27532 affectant le processus en écoute sur le port 9401 du serveur VEEAM permet à un attaquant non-authentifié d’extraire des identifiants stockés dans la base de données de la solution et de déclencher l’exécution de commandes arbitraires sur le serveur de sauvegarde. L’attaquant peut ensuite potentiellement utiliser ces informations pour disposer d&#8217;accès aux serveurs et infrastructures couverts par le système de sauvegarde et prendre le contrôle du serveur exécutant le service Veeam.</p>



<h2 class="wp-block-heading">Scenario d&#8217;exploitation</h2>



<p>La vulnérabilité, même si son exploitation n&#8217;est pas triviale est activement exploitée par au moins un groupe de ransomware, et plusieurs codes d&#8217;exploitation sont disponibles publiquement. Il est donc à craindre que les attaques automatisées se multiplient dans les prochaines semaines.</p>



<p>Le scénario d&#8217;exploitation observé consiste à déployer un exécutable sur le serveur VEEAM afin de récupérer les identifiants de l&#8217;infrastructure sauvegardée (code d&#8217;accès à vSphere, …), supprimer les machines virtuelles en cours d&#8217;execution, et enfin chiffrer les sauvegardes en demandant une rançon. Jusqu&#8217;à maintenant, nous avons identifié ce scénario uniquement sur des systèmes Windows où Veeam a pu être installé avec le port 9401 exposé sur Internet.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="423" src="https://blog.ovhcloud.com/wp-content/uploads/2023/05/Untitled-2023-05-10-1040-1024x423.png" alt="" class="wp-image-25275" srcset="https://blog.ovhcloud.com/wp-content/uploads/2023/05/Untitled-2023-05-10-1040-1024x423.png 1024w, https://blog.ovhcloud.com/wp-content/uploads/2023/05/Untitled-2023-05-10-1040-300x124.png 300w, https://blog.ovhcloud.com/wp-content/uploads/2023/05/Untitled-2023-05-10-1040-768x317.png 768w, https://blog.ovhcloud.com/wp-content/uploads/2023/05/Untitled-2023-05-10-1040.png 1403w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h2 class="wp-block-heading">Comment savoir si mon service est vulnérable</h2>



<p>Toutes les versions de Veeam Backup &amp; Replication antérieure à la 12.0.0.1420 P20230223 ou 11.0.1.1261 P20230227 sont vulnérables. Si le port 9401 est accessible depuis des adresses IP qui ne sont pas de confiance, le service est vulnérable.</p>



<h2 class="wp-block-heading">Résolution et Mitigation du risque</h2>



<p>Afin de vous protéger de cette attaque, une mise à jour de l’infrastructure de sauvegarde est nécessaire. Vous trouverez les binaires corrigés dans <a href="https://www.veeam.com/kb4424" data-wpel-link="external" target="_blank" rel="nofollow external noopener noreferrer">l’article officiel</a> publié par VEEAM.</p>



<p>En attendant la mise à jour de vos infrastructures, nous vous recommandons la mise en place des mesures suivantes :</p>



<p>Au niveau des serveurs de sauvegarde, nous vous recommandons d’éviter leur exposition sur des réseaux non sécurisés (ndlr : Réseaux publiques).</p>



<p>Par défaut, l&#8217;installation de VEEAM configure le firewall windows afin d&#8217;autoriser toutes les connexions entrantes sur les ports utilisés par la solution. </p>



<figure class="wp-block-gallery has-nested-images columns-default is-cropped wp-block-gallery-3 is-layout-flex wp-block-gallery-is-layout-flex">
<figure class="wp-block-image size-large is-style-default"><img loading="lazy" decoding="async" width="1024" height="506" data-id="25280" src="https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-091122-1-1024x506.png" alt="" class="wp-image-25280" srcset="https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-091122-1-1024x506.png 1024w, https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-091122-1-300x148.png 300w, https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-091122-1-768x379.png 768w, https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-091122-1.png 1213w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>
</figure>



<p>Nous vous recommandons d’appliquer des règles de filtrage afin de restreindre au strict minimum les services exposés.</p>



<p>Pour ce faire, assurez vous que le par-feu Windows de votre serveur de sauvegarde est activé et configuré pour bloquer les connexions entrantes ne correspondant à aucune règles.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="619" height="436" src="https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-091729.png" alt="" class="wp-image-25281" srcset="https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-091729.png 619w, https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-091729-300x211.png 300w" sizes="auto, (max-width: 619px) 100vw, 619px" /></figure>



<p>Assurez vous ensuite que les ports utilisés ne sont accessibles que depuis des serveurs de votre infrastructure. Pour un filtrage optimal vous pouvez vous référer à la <a href="https://helpcenter.veeam.com/docs/backup/vsphere/used_ports.html?ver=120" data-wpel-link="external" target="_blank" rel="nofollow external noopener noreferrer">documentation officielle.</a></p>



<figure class="wp-block-gallery has-nested-images columns-default is-cropped wp-block-gallery-4 is-layout-flex wp-block-gallery-is-layout-flex">
<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="745" height="586" data-id="25284" src="https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-092900.png" alt="" class="wp-image-25284" srcset="https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-092900.png 745w, https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-092900-300x236.png 300w" sizes="auto, (max-width: 745px) 100vw, 745px" /></figure>
</figure>



<p>Vous devriez voir la règle de filtrage maintenant restreinte à votre réseau</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1019" height="42" src="https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-093148-1.png" alt="" class="wp-image-25286" srcset="https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-093148-1.png 1019w, https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-093148-1-300x12.png 300w, https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-093148-1-768x32.png 768w" sizes="auto, (max-width: 1019px) 100vw, 1019px" /></figure>



<p>Si vous n’utilisez pas de mount server, nous vous recommandons de bloquer complètement le port 9401, sinon de le restreindre uniquement depuis l’adresse du/des mount server(s). Plus globalement, nous vous recommandons de bloquer tous les services que vous n&#8217;utilisez pas.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="92" src="https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-092654-1024x92.png" alt="" class="wp-image-25283" srcset="https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-092654-1024x92.png 1024w, https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-092654-300x27.png 300w, https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-092654-768x69.png 768w, https://blog.ovhcloud.com/wp-content/uploads/2023/05/Screenshot-2023-05-11-092654.png 1063w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p>Au niveau de l’infrastructure de virtualisation ou des stockages de destination, aucune mitigation n’est envisageable. L’attaquant utilisant des connexions légitimes, il n’est pas possible de les prévenir. Il est donc essentiel de sécuriser tout composant se connectant à ces services.</p>



<h2 class="wp-block-heading">En cas de compromission</h2>



<p>Si vous suspectez une compromission liée à cette attaque, nous vous recommandons de vous rapprocher du support au plus vite afin d&#8217;évaluer les solutions vous permettant éventuellement de récupérer vos données.</p>



<h2 class="wp-block-heading">Références supplémentaires :</h2>



<p><a href="https://www.veeam.com/kb4424" data-wpel-link="external" target="_blank" rel="nofollow external noopener noreferrer">https://www.veeam.com/kb4424</a><br><a href="https://helpcenter.veeam.com/docs/backup/vsphere/used_ports.html?ver=120" data-wpel-link="external" target="_blank" rel="nofollow external noopener noreferrer">https://helpcenter.veeam.com/docs/backup/vsphere/used_ports.html?ver=120</a></p>



<p><a href="https://www.ovhcloud.com/fr/enterprise/products/hosted-private-cloud/" data-wpel-link="external" target="_blank" rel="nofollow external noopener noreferrer">https://www.ovhcloud.com/fr/enterprise/products/hosted-private-cloud/</a><br><a href="https://www.ovhcloud.com/fr/enterprise/products/hosted-private-cloud/veeam-backup-managed/" data-wpel-link="external" target="_blank" rel="nofollow external noopener noreferrer">https://www.ovhcloud.com/fr/enterprise/products/hosted-private-cloud/veeam-backup-managed/</a><br><a href="https://www.ovhcloud.com/fr/storage-solutions/veeam-enterprise/" data-wpel-link="external" target="_blank" rel="nofollow external noopener noreferrer">https://www.ovhcloud.com/fr/storage-solutions/veeam-enterprise/</a></p>
<img loading="lazy" decoding="async" src="//blog.ovhcloud.com/wp-content/plugins/matomo/app/matomo.php?idsite=1&amp;rec=1&amp;url=https%3A%2F%2Fblog.ovhcloud.com%2Fvulnerabilite-sur-veeam-backup-replication%2F&amp;action_name=Vuln%C3%A9rabilit%C3%A9%20sur%20VEEAM%20Backup%20%26amp%3B%20Replication&amp;urlref=https%3A%2F%2Fblog.ovhcloud.com%2Ffeed%2F" style="border:0;width:0;height:0" width="0" height="0" alt="" />]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
